Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/7] linux: use the package infrastructure to download patches
Date: Sun, 15 Mar 2015 16:58:10 +0100	[thread overview]
Message-ID: <5505AC12.4080000@openwide.fr> (raw)
In-Reply-To: <20150315161406.37b68310@free-electrons.com>

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
> 

  reply	other threads:[~2015-03-15 15:58 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-28 18:15 [Buildroot] [PATCH 0/7] Improvements to the download logic Thomas Petazzoni
2015-02-28 18:15 ` [Buildroot] [PATCH 1/7] linux: use the package infrastructure to download patches Thomas Petazzoni
2015-02-28 19:54   ` Baruch Siach
2015-03-15 14:59   ` Romain Naour
2015-03-15 15:14     ` Thomas Petazzoni
2015-03-15 15:58       ` Romain Naour [this message]
2015-03-22 15:15       ` Arnout Vandecappelle
2015-03-15 16:44   ` Romain Naour
2015-03-22 15:16   ` Arnout Vandecappelle
2015-02-28 18:15 ` [Buildroot] [PATCH 2/7] pkg-generic: fix the logic showing the "Downloading" message Thomas Petazzoni
2015-03-15 16:44   ` Romain Naour
2015-03-22 15:19   ` Arnout Vandecappelle
2015-02-28 18:15 ` [Buildroot] [PATCH 3/7] pkg-generic: take into account <pkg>_EXTRA_DOWNLOADS to display " Thomas Petazzoni
2015-03-15 16:44   ` Romain Naour
2015-03-22 15:20   ` Arnout Vandecappelle
2015-02-28 18:15 ` [Buildroot] [PATCH 4/7] pkg-generic: refactor the "Downloading" message logic Thomas Petazzoni
2015-03-15 16:44   ` Romain Naour
2015-03-22 15:29   ` Arnout Vandecappelle
2015-02-28 18:15 ` [Buildroot] [PATCH 5/7] pkg-generic: allow full URLs for <pkg>_EXTRA_DOWNLOADS Thomas Petazzoni
2015-03-15 16:45   ` Romain Naour
2015-03-22 15:33   ` Arnout Vandecappelle
2015-02-28 18:15 ` [Buildroot] [PATCH 6/7] docs/manual: update documentation about <pkg>_SOURCE, <pkg>_PATCH and <pkg>_EXTRA_DOWNLOADS Thomas Petazzoni
2015-03-15 16:45   ` Romain Naour
2015-03-22 15:58   ` Arnout Vandecappelle
2015-02-28 18:15 ` [Buildroot] [PATCH 7/7] perl: use <pkg>_EXTRA_DOWNLOADS Thomas Petazzoni
2015-03-15 16:46   ` Romain Naour
2015-03-22 15:59   ` Arnout Vandecappelle

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=5505AC12.4080000@openwide.fr \
    --to=romain.naour@openwide.fr \
    --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