From: Peter Korsgaard <peter@korsgaard.com>
To: Brandon Maier via buildroot <buildroot@buildroot.org>
Cc: Brandon Maier <brandon.maier@collins.com>
Subject: Re: [Buildroot] [PATCH 3/3] package/pkg-kconfig: cleanup savedefconfig MAKE
Date: Mon, 02 Sep 2024 12:19:21 +0200 [thread overview]
Message-ID: <8734mis6hi.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20240729-pkg-kconfig-ppd-v1-3-36c901c73a7b@collins.com> (Brandon Maier via buildroot's message of "Mon, 29 Jul 2024 16:19:10 +0000")
>>>>> "Brandon" == Brandon Maier via buildroot <buildroot@buildroot.org> writes:
> The kconfig infra defines a 'PKG_KCONFIG_MAKE' var that wraps all the
> standard kconfig options. Switch to this so we aren't duplicating the
> logic.
> Signed-off-by: Brandon Maier <brandon.maier@collins.com>
Committed to 2024.02.x and 2024.05.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-09-02 10:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 16:19 [Buildroot] [PATCH 0/3] package/pkg-kconfig: fixes for per-package-directory Brandon Maier via buildroot
2024-07-29 16:19 ` [Buildroot] [PATCH 1/3] package/pkg-kconfig: fix *-savedefconfig under ppd Brandon Maier via buildroot
2024-09-02 10:19 ` Peter Korsgaard
2024-07-29 16:19 ` [Buildroot] [PATCH 2/3] package/pkg-kconfig: fix *-diff-config " Brandon Maier via buildroot
2024-09-02 10:19 ` Peter Korsgaard
2024-07-29 16:19 ` [Buildroot] [PATCH 3/3] package/pkg-kconfig: cleanup savedefconfig MAKE Brandon Maier via buildroot
2024-09-02 10:19 ` Peter Korsgaard [this message]
2024-07-29 18:10 ` [Buildroot] [PATCH 0/3] package/pkg-kconfig: fixes for per-package-directory Thomas Petazzoni via buildroot
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=8734mis6hi.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=brandon.maier@collins.com \
--cc=buildroot@buildroot.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.