From: W.P. <laurentp@wp.pl>
To: buildroot@busybox.net
Subject: [Buildroot] [OT?] Re: Applying custom kernel patches
Date: Fri, 04 Mar 2011 23:39:19 +0100 [thread overview]
Message-ID: <4D716A17.1040008@wp.pl> (raw)
In-Reply-To: <518665.81144.qm@web161818.mail.bf1.yahoo.com>
U?ytkownik Steve Calfee napisa?:
>> From: bruce bushby <bruce.bushby@gmail.com>
>>
>
>
>> I've tried placing my patches in:
>> /opt/buildroot/linux/kernel-patches/0001-linux-2.6.38-rc5.patch
>>
>>
>> I also tried putting them in
>> /opt/buildroot/package/linux/kernel-patches/0001-linux-2.6.38-rc5.patch
>>
>>
> Hi,
>
> You may have a path problem for your patches. The path should be given in your
> *_defconfig.
>
>
> And buildroot will automatically apply patches at the appropriate time if they
> are named in the form linux*patch. See the makefile.
>
> so 0001-linux-2.6.38-rc5.patch should be linux-001-2.6.38-rc5.patch
>
> Regards, Steve
>
>
Could someone write a HOWTO?
I mean:
step 0): "I have kernel.xxx.yy.zzz directory unpacked AND a set of
patches (that applies correctly from kernel root) patch.00xx.patch"
step 1): where should I put (link?) kernel source?,
step 2): where should I put patches?.
step 3): how do I inform buildroot about patches?
W.P.
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
next prev parent reply other threads:[~2011-03-04 22:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 21:15 [Buildroot] Applying custom kernel patches bruce bushby
2011-03-04 21:52 ` ANDY KENNEDY
2011-03-04 22:06 ` bruce bushby
2011-03-04 22:13 ` ANDY KENNEDY
2011-03-07 13:43 ` Thomas Petazzoni
2011-03-04 22:21 ` Steve Calfee
2011-03-04 22:39 ` W.P. [this message]
2011-03-04 22:45 ` [Buildroot] [OT?] " ANDY KENNEDY
2011-03-04 22:59 ` Yann E. MORIN
2011-03-04 23:19 ` bruce bushby
2011-03-04 23:02 ` bruce bushby
2011-03-04 23:21 ` W.P.
2011-03-04 22:56 ` Steve Calfee
2011-03-07 13:50 ` Thomas Petazzoni
2011-03-07 21:46 ` Steve Calfee
2011-03-07 13:48 ` [Buildroot] " Thomas Petazzoni
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=4D716A17.1040008@wp.pl \
--to=laurentp@wp.pl \
--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