Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Joao Pinto <Joao.Pinto@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] Kernel patches in Buildroot
Date: Wed, 18 Nov 2015 09:30:21 +0000	[thread overview]
Message-ID: <564C452D.1050908@synopsys.com> (raw)
In-Reply-To: <20151117210817.26557c68@free-electrons.com>

Dear Thomas,
Thanks, worked fine!

BR
Joao Pinto

On 11/17/2015 8:08 PM, Thomas Petazzoni wrote:
> Dear Joao Pinto,
> 
> On Tue, 17 Nov 2015 17:13:31 +0000, Joao Pinto wrote:
> 
>> BR2_GLOBAL_PATCH_DIR="snps-custom/packages"
>>
>> I have a "snps-custom" folder which has a "packages" folder inside. Inside the
>> "packages" folder we have a folder for each package we need to patch, in this
>> example mplayer and the linux kernel.
>>
>> --snps-custom
>>   --packages
>>     --linux-arc-axs101-20141021-3.13
> 
> Call this folder just "linux". The folder must be named after the
> package name, and not contains some additional version information. If
> you want to store patches for several versions of the same package, you
> must use the same organization as in Buildroot itself:
> 
>   <package-name>/<package-version>/*.patch
> 
> Best regards,
> 
> Thomas
> 

      reply	other threads:[~2015-11-18  9:30 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
2015-11-17 20:18           ` David Van Arnem
2015-11-17 20:08       ` Thomas Petazzoni
2015-11-18  9:30         ` Joao Pinto [this message]

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=564C452D.1050908@synopsys.com \
    --to=joao.pinto@synopsys.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