Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Niklas Cassel <niklas.cassel@wdc.com>,
	Damien Le Moal <damien.lemoal@wdc.com>,
	Mark Corbin <mark@dibsco.co.uk>,
	Jonathan Ben Avraham <yba@tkos.co.il>,
	buildroot@buildroot.org,
	Giulio Benetti <giulio.benetti@benettiengineering.com>,
	Romain Naour <romain.naour@gmail.com>,
	Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
Subject: Re: [Buildroot] [PATCH v2 4/4] arch: rework MMU option handling and move to "Target architecture" menu
Date: Wed, 27 Jul 2022 11:35:41 +0200	[thread overview]
Message-ID: <20220727093541.GE1085273@scaer> (raw)
In-Reply-To: <20220727112207.309f4ec4@windsurf>

Thomas, All,

On 2022-07-27 11:22 +0200, Thomas Petazzoni spake thusly:
> On Wed, 27 Jul 2022 10:30:20 +0200
> "Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> > I am not sure why you are removing a generic option in favour of two
> > arch-specific options that behave exactly the same.
> The motivation is explained in the commit log. Quoting it
> ================================================================
> However, if we simply move it in arch/Config.in, it means that we
> would have the following order of options:
> 
>  Target architecture
>  Target architecture variant
>  ABI
>  MMU
>  Binary format

Let me complete that for you, then:

   ... where variant and ABI are arch-specific, so we can't have a
    generic option in-between, because a kconfig option can be given a
    single prompt (even conditional ones), and appears in the menuconfig
    at the place it was given its prompt.

OK, got it now. Thanks!

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-07-27  9:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26 16:39 [Buildroot] [PATCH v2 1/4] arch/Config.in.riscv: lp64f ABI is only supported if MMU is enabled Thomas Petazzoni via buildroot
2022-07-26 16:39 ` [Buildroot] [PATCH v2 2/4] package/Makefile.in: add detection for the lack of C library Thomas Petazzoni via buildroot
2022-07-27  7:58   ` Yann E. MORIN
2022-07-27  8:24     ` Thomas Petazzoni via buildroot
2022-08-29 20:15   ` Peter Korsgaard
2022-07-26 16:39 ` [Buildroot] [PATCH v2 3/4] arch/Config.in: move the binary format selection further down Thomas Petazzoni via buildroot
2022-07-27  7:58   ` Yann E. MORIN
2022-07-26 16:39 ` [Buildroot] [PATCH v2 4/4] arch: rework MMU option handling and move to "Target architecture" menu Thomas Petazzoni via buildroot
2022-07-27  7:03   ` Damien Le Moal via buildroot
2022-07-27  8:30   ` Yann E. MORIN
2022-07-27  9:22     ` Thomas Petazzoni via buildroot
2022-07-27  9:35       ` Yann E. MORIN [this message]
2022-07-27  9:43   ` Yann E. MORIN
2022-07-27  9:55     ` Thomas Petazzoni via buildroot
2022-07-27  7:57 ` [Buildroot] [PATCH v2 1/4] arch/Config.in.riscv: lp64f ABI is only supported if MMU is enabled Yann E. MORIN
2022-08-29 20:13 ` Peter Korsgaard

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=20220727093541.GE1085273@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=damien.lemoal@wdc.com \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=mark@dibsco.co.uk \
    --cc=niklas.cassel@wdc.com \
    --cc=romain.naour@gmail.com \
    --cc=thomas.de_schampheleire@nokia.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yba@tkos.co.il \
    /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