Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot] Kernel Patches Not Applied
@ 2015-02-26 18:29 Crast, Nicholas
  2015-03-02 20:37 ` Arnout Vandecappelle
  0 siblings, 1 reply; 2+ messages in thread
From: Crast, Nicholas @ 2015-02-26 18:29 UTC (permalink / raw)
  To: buildroot

Hi all,

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.

My patch is in the following folder:
board/sensis/patches/linux-custom-0001-spi.patch

I have tried the filename linux-0001-spi.patch as well.

Here is the relevant section of my .config file:
BR2_GLOBAL_PATCH_DIR=""
BR2_LINUX_KERNEL_PATCH="board/sensis/patches"

When I run make linux-dirclean linux-patch, I get the following output:
rm -Rf /home/nick/buildroot-2014.11/output/build/linux-custom
>>> linux custom Syncing from source dir linux/linux-socfpga-socfpga-3.16-94ca8d7
rsync -au --exclude .svn --exclude .git --exclude .hg --exclude .bzr --exclude CVS linux/linux-socfpga-socfpga-3.16-94ca8d7/ /home/nick/buildroot-2014.11/output/build/linux-custom
touch /home/nick/buildroot-2014.11/output/build/linux-custom/.stamp_rsynced


I see nothing about it even attempting to patch. Any ideas what I am doing wrong?

Thanks,
Nick

---------------------------------------
Nick Crast
Software Engineer
Saab Sensis Corporation
Phone: 315-445-5703
Email: Nicholas.Crast at saabsensis.com<mailto:Nicholas.Crast@saabsensis.com>


This message is intended only for the addressee and may contain information that is company confidential or privileged. Any technical data in this message may be exported only in accordance with the U.S. International Traffic in Arms Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15 CFR Parts 730-774). Unauthorized use is strictly prohibited and may be unlawful. If you are not the intended recipient, or the person responsible for delivering to the intended recipient, you should not read, copy, disclose or otherwise use this message. If you have received this email in error, please delete it, and advise the sender immediately.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150226/0f1e32c7/attachment.html>

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [Buildroot] Kernel Patches Not Applied
  2015-02-26 18:29 [Buildroot] Kernel Patches Not Applied Crast, Nicholas
@ 2015-03-02 20:37 ` Arnout Vandecappelle
  0 siblings, 0 replies; 2+ messages in thread
From: Arnout Vandecappelle @ 2015-03-02 20:37 UTC (permalink / raw)
  To: buildroot

 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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2015-03-02 20:37 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-02-26 18:29 [Buildroot] Kernel Patches Not Applied Crast, Nicholas
2015-03-02 20:37 ` Arnout Vandecappelle

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox