From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Kernel patches in Buildroot
Date: Wed, 11 Nov 2015 13:04:35 +0100 [thread overview]
Message-ID: <56432ED3.7070008@mind.be> (raw)
In-Reply-To: <56432809.3000902@synopsys.com>
On 11-11-15 12:35, Joao Pinto wrote:
> Hi,
> We are designing the procedure to release our software stack based on buildroot.
> Could you please tell what is the advised method for including a kernel patch
> set in buildroot? I typically use BR2_LINUX_KERNEL_PATCH where I indicate each
> patch file. Is there a easier way like using BR2_GLOBAL_PATCH_DIR for example?
I personally prefer to use a git repository that includes the patches. During
development, I make a local checkout specified with LINUX_OVERRIDE_SRCDIR; for
release, I point to the repository (often on gitlab) and specify a tag.
BR2_GLOBAL_PATCH_DIR and BR2_LINUX_KERNEL_PATCH are basically equivalent, you
can specify a directory with the latter as well.
Regards,
Arnout
>
> Thanks for your help!
>
> Joao
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2015-11-11 12:04 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 [this message]
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
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=56432ED3.7070008@mind.be \
--to=arnout@mind.be \
--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