From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Kernel Patches Not Applied
Date: Mon, 02 Mar 2015 21:37:24 +0100 [thread overview]
Message-ID: <54F4CA04.8050601@mind.be> (raw)
In-Reply-To: <36A43B0E1E88D84791516F9D44BC48331B4A722A@corpmail01.corp.sensis.com>
Hi Nicholas,
On 26/02/15 19:29, Crast, Nicholas wrote:
> I am currently using buildroot-2014.11, and I am having issues patching my
> kernel. My kernel is a custom (untarred) source, so the build output is in
> output/build/linux-custom.
Patches are not applied on a custom local source tree
(BR2_LINUX_KERNEL_CUSTOM_LOCAL). The typical use case for this is when you have
a local checkout of the source code which is managed by something like git
submodules or gerrit or whatnot.
If you want to apply patches to a custom source tree, use
BR2_LINUX_KERNEL_CUSTOM_TARBALL with a file: or scp: URL.
Regards,
Arnout
[snip]
--
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: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
prev parent reply other threads:[~2015-03-02 20:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 18:29 [Buildroot] Kernel Patches Not Applied Crast, Nicholas
2015-03-02 20:37 ` Arnout Vandecappelle [this message]
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=54F4CA04.8050601@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox