All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH RFC next] package/linux: drop useless intermediate DTS booleans
Date: Mon, 26 Feb 2018 18:57:07 +0100	[thread overview]
Message-ID: <20180226185707.75c792db@windsurf.lan> (raw)
In-Reply-To: <20180226174721.5785-1-yann.morin.1998@free.fr>

Hello,

On Mon, 26 Feb 2018 18:47:21 +0100, Yann E. MORIN wrote:
> Just use whatever the user specified in the list. An empty list means no
> DTS was specified.
> 
> No need to add legacy option, as the behaviour does not change.
> 
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Simon van der Veldt <simon.vanderveldt@gmail.com>
> Cc: Arnout Vandecappelle <arnout@mind.be>
> Cc: Peter Korsgaard <peter@korsgaard.com>
> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> 
> ---
> This is an RFC patch, totally untested, as an attempt to fix the fallout
> of allowing both in-tree and out-of-tree DTS files at the same time.
> It's here just to kickstart a discussion, especially about the help
> texts... ;-)

Yes, I agree with this direction. When I saw the patch allowing to
generate both in-tree and out of tree DTS, I also thought "but why do
we keep those booleans". Next time I should not only "think" but also
write it in an e-mail as a reply to the patch :-)

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com

  reply	other threads:[~2018-02-26 17:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-26 17:47 [Buildroot] [PATCH RFC next] package/linux: drop useless intermediate DTS booleans Yann E. MORIN
2018-02-26 17:57 ` Thomas Petazzoni [this message]
2018-03-07 22:45 ` Joshua.Henderson at microchip.com
2018-03-08  8:08   ` Peter Korsgaard
2018-03-30 19:24 ` 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=20180226185707.75c792db@windsurf.lan \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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.