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 v4 1/1] Added linux drivers backports project
Date: Mon, 20 Apr 2015 22:56:28 +0200	[thread overview]
Message-ID: <20150420225628.0a54561f@free-electrons.com> (raw)
In-Reply-To: <553564B4.2060303@mind.be>

Dear Arnout Vandecappelle,

On Mon, 20 Apr 2015 22:42:28 +0200, Arnout Vandecappelle wrote:

>  However, we can add the dependency specifically for linux-backports. There is
> something to be said for the reasoning that usually/sometimes you don't need the
> dependencies to be present, so doing it per package sounds OK.
> 
>  So in this case, adding
> 
> $(LINUX_BACKPORTS_KCONFIG_FILE): linux
> 
> to linux-backports.mk should be sufficient.

If we do this, we must also keep the 'linux' dependency in
LINUX_BACKPORTS_DEPENDENCIES as well, so that the package infra remains
aware of this dependency.

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

  reply	other threads:[~2015-04-20 20:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-17 23:01 [Buildroot] [PATCH v4 1/1] Added linux drivers backports project Petr Vorel
2015-04-19  9:03 ` Thomas Petazzoni
2015-04-19 13:15   ` Yann E. MORIN
2015-04-19 16:20   ` Arnout Vandecappelle
2015-04-19 16:28     ` Yann E. MORIN
2015-04-19 17:03       ` Thomas Petazzoni
2015-04-19 21:19         ` Petr Vorel
2015-04-19 21:28           ` Yann E. MORIN
2015-04-20 20:42         ` Arnout Vandecappelle
2015-04-20 20:56           ` Thomas Petazzoni [this message]
2015-04-20 21:08             ` Arnout Vandecappelle
2015-04-20 21:00           ` Yann E. MORIN

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=20150420225628.0a54561f@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