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 suggestion : series file ->make it a variable
Date: Fri, 16 Aug 2013 12:56:52 +0200	[thread overview]
Message-ID: <20130816125652.701e7173@skate> (raw)
In-Reply-To: <FAC1EE0BD8A0431EBFF14BEE70571910@JohanW7>

Dear Sagaert Johan,

On Fri, 16 Aug 2013 12:19:13 +0200, Sagaert Johan wrote:

> Now I use a 'series'  file in my board directory to specify what patches that should be applied to the kernel.
> I would love to see a menu entry where I can specify what list of patches that should be applied.(default value :series)

What's the difference between what you're asking and the already
existing BR2_LINUX_KERNEL_PATCH configuration option?

config BR2_LINUX_KERNEL_PATCH
        string "Custom kernel patches"
        help
          A space-separated list of patches to apply to the
          kernel. Each patch can be described as an URL, a local file
          path, or a directory. In the case of a directory, all files
          matching linux-*.patch in the directory will be applied.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-08-16 10:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-16 10:19 [Buildroot] kernel patches suggestion : series file ->make it a variable Sagaert Johan
2013-08-16 10:56 ` Thomas Petazzoni [this message]
2013-08-16 20:04   ` Sagaert Johan
2013-08-16 20:12     ` Yann E. MORIN
2013-08-18  0:26       ` Sagaert Johan
2013-08-22 19:07         ` Ralph Siemsen

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=20130816125652.701e7173@skate \
    --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.