Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Nayab Sayed via buildroot <buildroot@buildroot.org>
Cc: Nayab Sayed <nayabbasha.sayed@microchip.com>
Subject: Re: [Buildroot] [PATCH v2] package/busybox: refresh busybox.config
Date: Thu, 9 May 2024 16:14:26 +0200	[thread overview]
Message-ID: <20240509161426.14b7e757@windsurf> (raw)
In-Reply-To: <20240509-refresh-busybox-config-v2-1-71a4c8061ac7@microchip.com>

On Thu, 9 May 2024 11:27:01 +0530
Nayab Sayed via buildroot <buildroot@buildroot.org> wrote:

> Refresh busybox.config to current version (1.36.1) default values.
> 
> Signed-off-by: Nayab Sayed <nayabbasha.sayed@microchip.com>
> ---
> When `make busybox-update-config` is executed, the config
> CONFIG_UDHCPC6_DEFAULT_SCRIPT became empty. But it's updated to reuse the
> value from earlier bump as mentioned in the commit d68b617993bd
> (package/busybox: update to 1.36.0).
> ---
> Changes in v2:
> - remove local custom config
> - Link to v1: https://lore.kernel.org/r/20240426-refresh-busybox-config-v1-1-c70cb5b60243@microchip.com
> ---
>  package/busybox/busybox.config | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)

Applied to master, thanks.

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

      reply	other threads:[~2024-05-09 14:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-09  5:57 [Buildroot] [PATCH v2] package/busybox: refresh busybox.config Nayab Sayed via buildroot
2024-05-09 14:14 ` 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=20240509161426.14b7e757@windsurf \
    --to=buildroot@buildroot.org \
    --cc=nayabbasha.sayed@microchip.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox