From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] linux: add fbtft kernel extension
Date: Sat, 10 Jan 2015 22:00:59 +0100 [thread overview]
Message-ID: <20150110220059.6aa33cb3@free-electrons.com> (raw)
In-Reply-To: <trinity-2bbfe20d-7483-4696-96fd-10d5a86139a3-1420922912380@3capp-gmx-bs51>
Dear Peter Seiderer,
On Sat, 10 Jan 2015 21:48:32 +0100, Peter Seiderer wrote:
> > - Remove the mention of CONFIG_SPI_BCM2708, since this makes the
> > description RaspberryPi specific, while these drivers can work
> > with any SPI controller.
>
> Maybe add some hint to not forget to enable platform specific spi driver
> would be helpful?
Sure, feel free to send some follow-up patch.
> > - Change the license to GPLv2, since it's kernel code.]
>
> Mhhh, in some way your are right, but it seems wrong for me that the
> buildroot license entry does not reflect what the package author stated
> in his own files....what would be the right buildroot entry in case
> of dual-license files?
That's a good question. I really wonder how the original author can
license those files under GPLv2+, while the kernel license is GPLv2
only. I think the original author is wrong on this.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-01-10 21:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-10 20:48 [Buildroot] [PATCH v3] linux: add fbtft kernel extension Peter Seiderer
2015-01-10 21:00 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-01-11 13:16 Peter Seiderer
2015-01-11 14:00 ` Richard Fergusson
2015-01-11 5:34 Richard Fergusson
2015-01-05 13:45 Peter Seiderer
2015-01-03 20:01 Peter Seiderer
2015-01-10 14:27 ` Thomas Petazzoni
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=20150110220059.6aa33cb3@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox