From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/7] package/linux: don't enforce check for DTS when not building
Date: Mon, 13 Jul 2015 09:18:58 +0200 [thread overview]
Message-ID: <20150713071858.GG4008@free.fr> (raw)
In-Reply-To: <20150713033718.GE2451@tarshish>
Baruch, All,
On 2015-07-13 06:37 +0300, Baruch Siach spake thusly:
> On Mon, Jul 13, 2015 at 01:44:31AM +0200, Arnout Vandecappelle wrote:
> > On 07/12/15 22:03, Baruch Siach wrote:
> > > On Sun, Jul 12, 2015 at 02:11:24PM +0200, Yann E. MORIN wrote:
> > >> Currently, this is triggering the error message:
> > >> make randconfig
> > >> make source
> > >>
> > >> Limit the checks that enforce a DTS is set and at most one DTB is
> > >> appended to when we are actually building, like is done for the
> > >> configuration-file variables.
> > >>
> > >> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> > >
> > > [snip]
> > >
> > >> -ifeq ($(BR2_LINUX_KERNEL_DTS_SUPPORT)$(KERNEL_DTS_NAME),y)
> > >> +ifeq ($(BR_BUILDING)$(BR2_LINUX_KERNEL_DTS_SUPPORT)$(KERNEL_DTS_NAME),yy)
> > >
> > > yy means that exactly two of these must be 'y'. Is that intended?
> >
> > Yes it is, because KERNEL_DTS_NAME is a string, not a boolean, so it
> > essentially checks that it is empty and DTS_SUPPORT is selected. But admittedly
> > it's not very transparent, it would make sense to add delimiters in-between at
> > least.
>
> Thanks for the explanation. A comment would be helpful here, I guess.
>
> Shouldn't we protect the code against someone naming a DTS just 'y'?
Yeah, we already discussed that with Thomas (live, we're in the same
place for a few days), and we've come to the conclusion that this
construct is indeed too tricky, and that we need a simpler code.
Your comments are now confirming this. ;-)
I'll rework the series shortly.
Thanks! :-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2015-07-13 7:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-12 12:11 [Buildroot] [PATCH 0/7] core/kconfig: fix display of custom error messages (branch yem/misc) Yann E. MORIN
2015-07-12 12:11 ` [Buildroot] [PATCH 1/7] core/pkg-kconfig: don't enforce check for config file when not building Yann E. MORIN
2015-07-12 12:11 ` [Buildroot] [PATCH 2/7] package/linux: don't enforce check for DTS " Yann E. MORIN
2015-07-12 20:03 ` Baruch Siach
2015-07-12 23:44 ` Arnout Vandecappelle
2015-07-13 3:37 ` Baruch Siach
2015-07-13 7:18 ` Yann E. MORIN [this message]
2015-07-12 12:11 ` [Buildroot] [PATCH 3/7] boot/at91boostrap3: check for config file before calling kconfig-package Yann E. MORIN
2015-07-12 12:11 ` [Buildroot] [PATCH 4/7] boot/barebox: " Yann E. MORIN
2015-07-12 12:11 ` [Buildroot] [PATCH 5/7] package/linux: " Yann E. MORIN
2015-07-12 12:11 ` [Buildroot] [PATCH 6/7] package/busybox: " Yann E. MORIN
2015-07-12 12:11 ` [Buildroot] [PATCH 7/7] package/uclibc: " Yann E. MORIN
2015-07-12 20:06 ` Baruch Siach
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=20150713071858.GG4008@free.fr \
--to=yann.morin.1998@free.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox