Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Added linux drivers backports project
Date: Fri, 17 Apr 2015 11:14:58 +0200	[thread overview]
Message-ID: <5530CF12.20307@mind.be> (raw)
In-Reply-To: <20150417090337.GA27179@vorel-pc>

On 17/04/15 11:03, Petr Vorel wrote:
> Thanks for comments, I'll create new version tonight.
> 
>>  I would say that this package fits better in the linux extensions menu. Even if
>> you just consider this package as a set of kernel modules, I think that from a
>> users perspective it fits better together with the kernel.
> Sounds reasonable, I'll do it.

 Well, Thomas disagrees, so I guess you shouldn't.

 Anyway, if it does become a Linux extension, the package will stay. One of the
Kconfig options (the package or the linux extension) will be a blind option, and
at that time we can still choose which one will be blind.

[snip]
>>> +# Checks to give errors that the user can understand
>>> +ifeq ($(filter source,$(MAKECMDGOALS)),)
>>> +ifeq ($(BR2_PACKAGE_LINUX_BACKPORTS_USE_DEFCONFIG),y)
>>> +ifeq ($(call qstrip,$(BR2_PACKAGE_LINUX_BACKPORTS_DEFCONFIG)),)
>>> +$(error No kernel defconfig name specified, check your BR2_PACKAGE_LINUX_BACKPORTS_DEFCONFIG setting)
>>> +endif
>>> +endif
>>> +
>>> +ifeq ($(BR2_PACKAGE_LINUX_BACKPORTS_USE_CUSTOM_CONFIG),y)
>>> +ifeq ($(call qstrip,$(BR2_PACKAGE_LINUX_BACKPORTS_CUSTOM_CONFIG_FILE)),)
>>> +$(error No kernel configuration file specified, check your BR2_PACKAGE_LINUX_BACKPORTS_CUSTOM_CONFIG_FILE setting)
>>> +endif
>>> +endif
>>> +
>>> +endif
> I'd keep the error messages as indication for user.

 If you use kconfig-package you should never get these messages because it
already has that check, on line 70-74:

# FOO_KCONFIG_FILE is required
ifndef $(2)_KCONFIG_FILE
$$(error Internal error: no value specified for $(2)_KCONFIG_FILE)
endif


 Oh, now I see that Yann's patch to convert this to ifeq hasn't been applied
yet... So yes in that case the custom check should stay.

 Regards,
 Arnout
-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2015-04-17  9:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-15 21:55 [Buildroot] [PATCH 0/1] Added linux drivers backports project Petr Vorel
2015-04-15 21:55 ` [Buildroot] [PATCH 1/1] " Petr Vorel
2015-04-16 20:29   ` Arnout Vandecappelle
2015-04-17  8:01     ` Thomas Petazzoni
2015-04-17  9:03     ` Petr Vorel
2015-04-17  9:14       ` Arnout Vandecappelle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-04-17  9:33 Petr Vorel
2015-04-17  9:33 ` Petr Vorel
2015-04-17 19:44 ` Arnout Vandecappelle
2015-04-17  9:40 Petr Vorel
2015-04-17  9:40 ` Petr Vorel
2015-04-17 19:35   ` Arnout Vandecappelle
2015-04-17 23:02     ` Petr Vorel

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=5530CF12.20307@mind.be \
    --to=arnout@mind.be \
    --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