Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5 1/1] ktap: new package
Date: Tue, 10 Dec 2013 17:54:47 +0100	[thread overview]
Message-ID: <52A74757.8030100@mind.be> (raw)
In-Reply-To: <CAAXf6LWTJ9SdNKmZ-ys1v+siYzj4eST2mhcCP0uFCszkb_TJSA@mail.gmail.com>

On 10/12/13 15:49, Thomas De Schampheleire wrote:
> On Tue, Dec 10, 2013 at 3:42 PM, Peter Korsgaard <jacmet@uclibc.org> wrote:
>>>>>>> "Thomas" == Thomas De Schampheleire <patrickdepinguin@gmail.com> writes:
>>
>> Hi,
>>
>>   > The first seems to emphasize that we require a Linux kernel to be
>>   > built in buildroot, while the second one leaves it in the middle. For
>>   > packages that actually build kernel modules, like ktap, we really need
>>   > the kernel inside buildroot, right? Are there any packages that depend
>>   > on BR2_LINUX_KERNEL that do _not_ require an in-buildroot kernel?
>>
>> I don't think so, as BR2_LINUX_KERNEL is the symbol to build a linux
>> kernel internally.
>
> Ok, sounds logical.
> So what is the best comment text? Simply:
> "foo needs a Linux kernel to be built"

  Sounds good to me. "to be built by buildroot" would be more accurate 
but probably too verbose.

  Regards,
  Arnout

> ?
>
> If we can agree on something I will submit a patch to make this consistent.
>
> Thanks,
> thomas
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>


-- 
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:[~2013-12-10 16:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-10 11:59 [Buildroot] [PATCH v5 1/1] ktap: new package Anders Darander
2013-12-10 12:35 ` Peter Korsgaard
2013-12-10 12:55   ` Anders Darander
2013-12-10 13:01     ` Jeremy Rosen
2013-12-10 13:39       ` Peter Korsgaard
2013-12-10 14:36         ` Thomas De Schampheleire
2013-12-10 14:42           ` Peter Korsgaard
2013-12-10 14:49             ` Thomas De Schampheleire
2013-12-10 16:54               ` Arnout Vandecappelle [this message]
2013-12-10 20:50                 ` 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=52A74757.8030100@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