All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Kernel patches in Buildroot
Date: Tue, 17 Nov 2015 21:09:51 +0100	[thread overview]
Message-ID: <20151117210951.0150b687@free-electrons.com> (raw)
In-Reply-To: <564B7235.20209@cmlab.biz>

Dear David Van Arnem,

On Tue, 17 Nov 2015 11:30:13 -0700, David Van Arnem wrote:
> On 11/17/2015 10:13 AM, Joao Pinto wrote:

> > The linux kernel patching system does not recognizes the
> > packages/linux-arc-axs101-20141021-3.13 patch folder. Could you give me a help
> > on this?
> 
> I haven't done this myself, so I'm not completely sure if this is 
> correct, but there's an option to add custom kernel patches under 
> menuconfig -> Kernel -> Custom kernel patches.  I think to patch the 
> kernel you would need to set that value to the 
> snps-custom/packages/linux-arc-axs... path.

This is indeed another solution. But Joao was trying to use the
BR2_GLOBAL_PATCH_DIR mechanism, which allows to provide custom patches
for *any* package, and not only specifically for the Linux kernel.

Essentially, the "Custom kernel patches" mechanism you points to
predates the BR2_GLOBAL_PATCH_DIR mechanism. We keep it for
compatibility reasons, but generally consider BR2_GLOBAL_PATCH_DIR to
be the "better way".

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-11-17 20:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-11 11:35 [Buildroot] Kernel patches in Buildroot Joao Pinto
2015-11-11 12:04 ` Arnout Vandecappelle
2015-11-11 13:13   ` Yegor Yefremov
2015-11-17 11:13   ` Joao Pinto
2015-11-17 17:13     ` Joao Pinto
2015-11-17 18:30       ` David Van Arnem
2015-11-17 20:09         ` Thomas Petazzoni [this message]
2015-11-17 20:18           ` David Van Arnem
2015-11-17 20:08       ` Thomas Petazzoni
2015-11-18  9:30         ` Joao Pinto

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=20151117210951.0150b687@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.