Felix Held has submitted this change. ( https://review.coreboot.org/c/coreboot/+/78441?usp=email )
Change subject: util/kconfig: Fix README.md formatting ......................................................................
util/kconfig: Fix README.md formatting
Change-Id: I0c47a603cc6e6174cd4895ff9f44b5bc242c653e Signed-off-by: Richard Marko srk@48.io Reviewed-on: https://review.coreboot.org/c/coreboot/+/78441 Reviewed-by: Martin L Roth gaumless@gmail.com Tested-by: build bot (Jenkins) no-reply@coreboot.org --- M util/kconfig/README.md 1 file changed, 8 insertions(+), 3 deletions(-)
Approvals: Martin L Roth: Looks good to me, approved build bot (Jenkins): Verified
diff --git a/util/kconfig/README.md b/util/kconfig/README.md index 4d508a5..a02d903 100644 --- a/util/kconfig/README.md +++ b/util/kconfig/README.md @@ -13,7 +13,9 @@ in an already-configured tree (`quilt pop -a` should cleanly unapply them all) or manually if quilt doesn't have its tracking metadata around yet:
- $ for i in `ls patches/*.patch | tac`; do patch -p1 -R -i "$i"; done +```sh +for i in $( ls patches/*.patch | tac ); do patch -p1 -R -i "$i"; done +```
The result should be a subtree that, apart from a few coreboot specific files on our side (e.g. documentation, integration in our build system) @@ -23,9 +25,11 @@ `git log util/kconfig` output in our tree.
Assuming that you want to uprev from Linux 5.13 to 5.14, with a Linux git tree -available in ~/linux, +available in `~/linux`
- $ cd util/kconfig && (cd ~/linux/ && git diff v5.13..v5.14 scripts/kconfig) | patch -p2` +```sh +cd util/kconfig && (cd ~/linux/ && git diff v5.13..v5.14 scripts/kconfig) | patch -p2` +```
applies the changes to your local tree.
@@ -39,6 +43,7 @@ the tree has been upreved to.
## Adding a new patch + The format of the patches to kconfig is a mix of the headers produced by `git format-patch` and the patch format of quilt. However neither git nor quilt seems to have any functionality to directly produce a file in such a format