From mboxrd@z Thu Jan 1 00:00:00 1970 From: Romain Naour Date: Sun, 15 Mar 2015 16:58:10 +0100 Subject: [Buildroot] [PATCH 1/7] linux: use the package infrastructure to download patches In-Reply-To: <20150315161406.37b68310@free-electrons.com> References: <1425147313-17380-1-git-send-email-thomas.petazzoni@free-electrons.com> <1425147313-17380-2-git-send-email-thomas.petazzoni@free-electrons.com> <55059E3B.70108@openwide.fr> <20150315161406.37b68310@free-electrons.com> Message-ID: <5505AC12.4080000@openwide.fr> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Hello Thomas, Le 15/03/2015 16:14, Thomas Petazzoni a ?crit : > Dear Romain Naour, > > On Sun, 15 Mar 2015 15:59:07 +0100, Romain Naour wrote: > >> I know, it's not related to your patch but linux patches doesn't follow the new >> naming convention here. >> >> Do we want to keep the "linux-" prefix since linux is not really a package or >> get rid of it ? > > linux is really a package. humm... yes (hide) :) > >> It would be convenient to use linux patches generated by git format-patch >> command like for other packages. > > You in fact can already do that, if you use BR2_GLOBAL_PATCH_DIR. > > Regarding whether we should switch from linux-*.patch to *.patch, I > don't know. It might break the build for people having various patches > in the directory point by BR2_LINUX_KERNEL_PATCH. But maybe we should > break the build for them at some point, and get to a situation where we > are consistent. I use BR2_LINUX_KERNEL_PATCH which point to a directory that contains all patches for the kernel build for my target at work. I already made the mistake to forget to rename a new patch with the "linux-" prefix, because I added it like I do for other packages. But sure, it would break the build if we decide to fix this. Best regards, Romain > > Best regards, > > Thomas >