From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Tue, 20 Dec 2016 23:00:14 +0100 Subject: [Buildroot] [PATCH 1/1] uboot: fix custom patch dir legacy handling In-Reply-To: <87wpeu5l6a.fsf@dell.be.48ers.dk> References: <1482203412-5361-1-git-send-email-danomimanchego123@gmail.com> <87tw9z7yw6.fsf@dell.be.48ers.dk> <06d55d32-6d74-0daa-8770-5b7e56deab81@mind.be> <871sx271oc.fsf@dell.be.48ers.dk> <87wpeu5l6a.fsf@dell.be.48ers.dk> Message-ID: <20161220230014.030d3f0d@free-electrons.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Hello, On Tue, 20 Dec 2016 22:45:49 +0100, Peter Korsgaard wrote: > > I noticed it now because we are upgrading from 2014.05 to 2016.11. We > > use both the uboot custom patch dir feature (replaced) and the linux > > custom path feature (dropped, frowny face), so I'm hitting those right > > now. > > Ok. The replacement for both is simply BR2_GLOBAL_PATCH_DIR (with linux > patches under linux/ and u-boot patches under uboot/). Not completely true: the "linux custom path" feature is not replaced by BR2_GLOBAL_PATCH_DIR. If one wants to get the same functionality, i.e telling Buildroot to use the Linux kernel source code from an available local directory, then the only solution is to use LINUX_OVERRIDE_SRCDIR. Best regards, Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com