Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Giulio Benetti <giulio.benetti@benettiengineering.com>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Luca Ceresoli <luca@lucaceresoli.net>,
	Leon Anavi <leon.anavi@konsulko.com>,
	Jagan Teki <jagan@amarulasolutions.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 0/6] configs/olimex_*: fix uboot build failure on gitlab jobs
Date: Sun, 31 Oct 2021 18:46:26 +0100	[thread overview]
Message-ID: <0134fdf3-eed7-d84d-e676-e7f092e1a3e5@benettiengineering.com> (raw)
In-Reply-To: <20211031184200.12836d56@windsurf>

On 10/31/21 6:42 PM, Thomas Petazzoni wrote:
> Hello,
> 
> On Sun, 31 Oct 2021 01:46:44 +0200
> Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> 
>> Giulio Benetti (6):
>>    configs/olimex_a10_olinuxino: uboot 2021.10 needs openssl and python3
>>    configs/olimex_a13_olinuxino: uboot 2021.10 needs openssl, pylibfdt
>>      and python3
>>    configs/olimex_a20_olinuxino_lime2: uboot 2021.10 needs openssl
>>    configs/olimex_a20_olinuxino_lime: uboot 2021.10 needs openssl
>>    configs/olimex_a20_olinuxino_micro: uboot 2021.10 needs openssl,
>>      pylibfdt and python3
>>    configs/olimex_a33_olinuxino: uboot 2021.10 needs openssl and python3
> 
> I've applied the entire series, but I changed something: the options in
> a defconfig are not sorted alphabetically, but they are sorted in their
> "natural" order in a defconfig (when generated with "make
> savedefconfig").
> 
> Of course, those hand-edited defconfigs, with extra comments, makes
> using "make savedefconfig" bit less convenient, but still I think we
> should follow the ordering of option that "make savedefconfig"
> provides, which is based on the ordering of options in Config.in files.

Ok, thank you for pointing.

Kind regards
-- 
Giulio Benetti
Benetti Engineering sas
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2021-10-31 17:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-30 23:46 [Buildroot] [PATCH 0/6] configs/olimex_*: fix uboot build failure on gitlab jobs Giulio Benetti
2021-10-30 23:46 ` [Buildroot] [PATCH 1/6] configs/olimex_a10_olinuxino: uboot 2021.10 needs openssl and python3 Giulio Benetti
2021-10-30 23:46 ` [Buildroot] [PATCH 2/6] configs/olimex_a13_olinuxino: uboot 2021.10 needs openssl, pylibfdt " Giulio Benetti
2021-10-30 23:46 ` [Buildroot] [PATCH 3/6] configs/olimex_a20_olinuxino_lime2: uboot 2021.10 needs openssl Giulio Benetti
2021-10-30 23:46 ` [Buildroot] [PATCH 4/6] configs/olimex_a20_olinuxino_lime: " Giulio Benetti
2021-10-30 23:46 ` [Buildroot] [PATCH 5/6] configs/olimex_a20_olinuxino_micro: uboot 2021.10 needs openssl, pylibfdt and python3 Giulio Benetti
2021-10-30 23:46 ` [Buildroot] [PATCH 6/6] configs/olimex_a33_olinuxino: uboot 2021.10 needs openssl " Giulio Benetti
2021-10-31 17:42 ` [Buildroot] [PATCH 0/6] configs/olimex_*: fix uboot build failure on gitlab jobs Thomas Petazzoni
2021-10-31 17:46   ` Giulio Benetti [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=0134fdf3-eed7-d84d-e676-e7f092e1a3e5@benettiengineering.com \
    --to=giulio.benetti@benettiengineering.com \
    --cc=buildroot@buildroot.org \
    --cc=jagan@amarulasolutions.com \
    --cc=leon.anavi@konsulko.com \
    --cc=luca@lucaceresoli.net \
    --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