backports.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Pedersen <thomas@adapt-ip.com>
To: backports <backports@vger.kernel.org>
Cc: Hauke Mehrtens <hauke@hauke-m.de>, Luis Chamberlain <mcgrof@kernel.org>
Subject: [PATCH v2 04/15] Makefile.subtrees: document how to update kconfig
Date: Fri, 13 May 2022 09:05:12 -0700	[thread overview]
Message-ID: <20220513160523.2944694-5-thomas@adapt-ip.com> (raw)
In-Reply-To: <20220513160523.2944694-1-thomas@adapt-ip.com>

From: Luis Chamberlain <mcgrof@kernel.org>

Now that kconfig is a git sub tree document what we need to do
to update version of config. We use squash here so we don't
carry the kconfig tree update logs in our commit log.

Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
---
 Makefile.subtrees | 10 ++++++++++
 1 file changed, 10 insertions(+)
 create mode 100644 Makefile.subtrees

diff --git a/Makefile.subtrees b/Makefile.subtrees
new file mode 100644
index 000000000000..49bb13b36060
--- /dev/null
+++ b/Makefile.subtrees
@@ -0,0 +1,10 @@
+# If you need to use a git subtree, please add it here.
+add-kconfig-remote:
+	git remote add kconfig https://github.com/mcgrof/kconfig.git
+
+add-kconfig:
+	git subtree add --prefix=backport/kconf --squash kconfig master
+
+refresh-kconfig:
+	git fetch kconfig
+	git subtree pull --prefix=backport/kconf --squash kconfig master
-- 
2.30.2

--
To unsubscribe from this list: send the line "unsubscribe backports" in

  parent reply	other threads:[~2022-05-13 16:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-13 16:05 [PATCH v2 00/15] Resurrect Integration Mode v2 Thomas Pedersen
2022-05-13 16:05 ` [PATCH v2 01/15] backport/kconf: remove our version of kconfig Thomas Pedersen
2022-05-13 16:05 ` [PATCH v2 02/15] Squashed 'backport/kconf/' content from commit 98bda615 Thomas Pedersen
2022-05-13 16:05 ` [PATCH v2 03/15] kconfig: fix backport syntax to work with linux-next next-20220204 Thomas Pedersen
2022-05-13 16:05 ` Thomas Pedersen [this message]
2022-05-13 16:05 ` [PATCH v2 05/15] backport: define BACKPORT_DIR for Kconfig.integrate Thomas Pedersen
2022-05-13 16:05 ` [PATCH v2 06/15] gentree: update kconfig source var to new kconfig format Thomas Pedersen
2022-05-13 16:05 ` [PATCH v2 07/15] gentree: try to make patch operation idempotent in case of --clean Thomas Pedersen
2022-05-13 16:05 ` [PATCH v2 08/15] gentree: do not prefix Kernel.local symbols Thomas Pedersen
2022-05-13 16:05 ` [PATCH v2 09/15] lib/bpversion: calculate Kconfig.versions for next major version Thomas Pedersen
2022-05-13 16:05 ` [PATCH v2 10/15] backport: expose BP_MODULES in package mode only Thomas Pedersen
2022-05-13 16:05 ` [PATCH v2 11/15] kconfig: fix select conversion for BPAUTO_ symbols in integration mode Thomas Pedersen
2022-05-13 16:05 ` [PATCH v2 12/15] integration-patches: refresh integration patch Thomas Pedersen
2022-05-13 16:05 ` [PATCH v2 13/15] integration-patches: make patches per target kernel version Thomas Pedersen
2022-05-13 16:05 ` [PATCH v2 14/15] integration-patches: support 5.4 target kernel Thomas Pedersen
2022-05-13 16:05 ` [PATCH v2 15/15] patches: fixup skb list patch Thomas Pedersen
2022-05-13 16:37 ` [PATCH v2 00/15] Resurrect Integration Mode v2 Luis Chamberlain

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220513160523.2944694-5-thomas@adapt-ip.com \
    --to=thomas@adapt-ip.com \
    --cc=backports@vger.kernel.org \
    --cc=hauke@hauke-m.de \
    --cc=mcgrof@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).