From: Ludovic Desroches <ludovic.desroches@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] Patching kernel with a tarball containing multiple patches
Date: Thu, 10 Mar 2011 16:11:53 +0100 [thread overview]
Message-ID: <4D78EA39.6000904@atmel.com> (raw)
Hello,
During the buildroot developer day on Friday 29th October, you have
talked about the ability to use tarball containing multiple patches.
I have seen that something was done to allow to use a space-separated
list of patches. It's a good thing since I could download one patch and
a second one. The problem is that the second one is a tarball containing
multiples patches. The tar.bz2 file was not a problem for
patch-kernel.sh but it simply uses a bunzip2 -cd command. Using this one
instead of extracting the archive into a folder introduces some troubles
since the order of the patches is not conserved.
It will be great to use this option as following :
BR2_LINUX_KERNEL_PATCH="ftp://my_patches.tar.bz2 patches_to_apply"
Then we have all our patches for kernel 2.6.35 for example but if some
of them are integrated into next revisions as 2.6.35.2, we can skip
integrated patches by changing only the list.
What is your point of view about it? Do I miss something (maybe I can
already do that) ?
Regards
Ludovic Desroches
reply other threads:[~2011-03-10 15:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4D78EA39.6000904@atmel.com \
--to=ludovic.desroches@atmel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox