From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] board: add support for nanopi-m1-plus
Date: Mon, 10 Jul 2017 13:41:13 +0200 [thread overview]
Message-ID: <87tw2ktt7q.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAA4kGkp6Royw9_xPoRK2Fhg8Qk5MovKUm-XNGbaFegeA31UNDA@mail.gmail.com> (Chakra D.'s message of "Mon, 10 Jul 2017 16:58:01 +0530")
>>>>> "Chakra" == Chakra D <2chakrass@gmail.com> writes:
Hi,
>> Also, please put this patch in:
>>
>> board/friendlyarm/nanopi-m1-plus/linux/patches/
>>
>> and name it just 0001-<something>.patch (i.e without the linux- prefix).
>>
> Do we need additional "patches" directory here ? Is this a convention
> we need to follow for adding patches ?
This is for the generic (E.G. not specific to the Linux package)
BR2_GLOBAL_PATCH_DIR option. With this, it will look in
$BR2_GLOBAL_PATCH_DIR/linux for linux patches, and yes - Our convention
is to use board/<vendor>/<board>/patches for the toplevel BR2_GLOBAL_PATCH_DIR.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2017-07-10 11:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 18:04 [Buildroot] [PATCH] board: add support for nanopi-m1-plus Chakra Divi
2017-07-06 19:26 ` Thomas Petazzoni
2017-07-10 11:28 ` Chakra D
2017-07-10 11:35 ` Thomas Petazzoni
2017-07-10 11:41 ` Peter Korsgaard [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=87tw2ktt7q.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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.