Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] spidev_test: new package
Date: Tue, 14 Oct 2014 14:34:26 -0300	[thread overview]
Message-ID: <543D5EA2.5030804@zacarias.com.ar> (raw)
In-Reply-To: <5f5516c3-f0eb-478e-ae83-be53e797f4af@email.android.com>

On 10/14/2014 02:29 PM, Thomas De Schampheleire wrote:
>> +comment "spidev_test needs Linux kernel to be built"
> 
> This should be '... needs a Linux ...'

I'll fix it.

> Here I think we should define the license and if possible license files, if needed using a hook to copy the license from the kernel...

Well the kernel & linux-headers aren't defining them either :)
And perf (another kernel-source based package) isn't either.

> Good idea to make this a package. We once copied this test to our own test repo, but this makes more sense.

This is a "fragile" package though, a new enough kernel version against
older headers might not build because of missing spidev defines.
On the autobuilder side that's no problem since it depends on the kernel
being built which for the time being isn't the case, but it should
probably be noted as such.

Regards.

  reply	other threads:[~2014-10-14 17:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-14 15:45 [Buildroot] [PATCH] spidev_test: new package Gustavo Zacarias
2014-10-14 17:29 ` Thomas De Schampheleire
2014-10-14 17:34   ` Gustavo Zacarias [this message]
2014-10-14 17:57 ` Ryan Barnett
2014-10-14 19:54 ` Baruch Siach
2014-10-14 19:56   ` Gustavo Zacarias
2014-10-14 20:09     ` Baruch Siach
2014-10-14 20:14   ` Thomas De Schampheleire
2014-10-14 20:18     ` Gustavo Zacarias
2014-10-14 20:19     ` Baruch Siach
2014-10-17 21:55   ` Yann E. MORIN
2014-10-18 20:08     ` 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=543D5EA2.5030804@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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