From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v7 1/1] Added linux drivers backports project
Date: Fri, 3 Jul 2015 22:24:12 +0200 [thread overview]
Message-ID: <5596EF6C.1020905@mind.be> (raw)
In-Reply-To: <1435791533-25991-1-git-send-email-petr.vorel@gmail.com>
On 07/02/15 00:58, Petr Vorel wrote:
> https://backports.wiki.kernel.org
>
> Signed-off-by: Petr Vorel <petr.vorel@gmail.com>
> Cc: Arnout Vandecappelle <arnout@mind.be>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>
> ---
> TODO: still don't know how to handle dependency on linux .config.
It took me some time, but I finally understand what the issue is here...
It's a bug in the kconfig infra. The rule for generating the .config is kind of
spliced into the the usual configure step of a package. It already has a
dependency on the patch step, but it's still missing a dependency on the
dependencies.
I'll cook an untested patch, could you take that up in your series? It will
allow you to get rid of the _PATCH_DEPENDENCIES.
Regards,
Arnout
--
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: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2015-07-03 20:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 22:58 [Buildroot] [PATCH v7 1/1] Added linux drivers backports project Petr Vorel
2015-07-03 20:24 ` Arnout Vandecappelle [this message]
2015-07-03 22:04 ` Yann E. MORIN
2015-07-03 22:33 ` Yann E. MORIN
2015-07-06 23:18 ` Arnout Vandecappelle
2015-07-21 22:57 ` Petr Vorel
2015-07-19 13:29 ` Yann E. MORIN
2015-07-19 13:36 ` Yann E. MORIN
2015-07-21 22:01 ` Petr Vorel
2015-07-22 5:35 ` 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=5596EF6C.1020905@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.