Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Added linux drivers backports project
Date: Fri, 17 Apr 2015 10:01:08 +0200	[thread overview]
Message-ID: <20150417100108.46fe9fc8@free-electrons.com> (raw)
In-Reply-To: <55301BBB.4090705@mind.be>

Dear Arnout Vandecappelle,

On Thu, 16 Apr 2015 22:29:47 +0200, Arnout Vandecappelle wrote:

>  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. But also, if you ever
> want to add the possibility to link the backported drivers in the kernel itself
> (which I believe is supported by backports), then you really need it to be a
> kernel extension.
> 
>  The opinion of other developers may differ, though.

While I do understand the reasoning, I'm not so sure about the
conclusion. The linux extension stuff is really for things that needed
to be tightly integrated with the kernel build process, because it
requires patching the kernel (xenomai, rtai, etc.).

Here, it is much more like lttng-modules, or linux-fusion,
cryptodev-linux, ktap, sysdig and so on: a bunch of external modules
that can be built with no problem as separate packages from the kernel.

So I would actually tend to prefer keeping linux-backports as a package
in package/, like the author did.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-04-17  8:01 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 [this message]
2015-04-17  9:03     ` Petr Vorel
2015-04-17  9:14       ` Arnout Vandecappelle
  -- 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=20150417100108.46fe9fc8@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