All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Brandon Maier via buildroot <buildroot@buildroot.org>
Cc: Nathaniel Roach <nroach44@gmail.com>,
	Brandon Maier <brandon.maier@collins.com>
Subject: Re: [Buildroot] [PATCH 0/3] package/pkg-kconfig: fixes for per-package-directory
Date: Mon, 29 Jul 2024 20:10:22 +0200	[thread overview]
Message-ID: <20240729201022.172cd836@windsurf> (raw)
In-Reply-To: <20240729-pkg-kconfig-ppd-v1-0-36c901c73a7b@collins.com>

On Mon, 29 Jul 2024 16:19:07 +0000
Brandon Maier via buildroot <buildroot@buildroot.org> wrote:

> Brandon Maier (3):
>       package/pkg-kconfig: fix *-savedefconfig under ppd
>       package/pkg-kconfig: fix *-diff-config under ppd
>       package/pkg-kconfig: cleanup savedefconfig MAKE

Thanks a lot, series applied!

I'm wondering how many other custom make targets like that we have that
would be missing the definition of PKG :-/

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2024-07-29 18:10 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
2024-07-29 18:10 ` Thomas Petazzoni via buildroot [this message]

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=20240729201022.172cd836@windsurf \
    --to=buildroot@buildroot.org \
    --cc=brandon.maier@collins.com \
    --cc=nroach44@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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.