From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] board: add support for nanopi-m1-plus
Date: Mon, 10 Jul 2017 13:35:55 +0200 [thread overview]
Message-ID: <20170710133555.3819183c@windsurf.lan> (raw)
In-Reply-To: <CAA4kGkp6Royw9_xPoRK2Fhg8Qk5MovKUm-XNGbaFegeA31UNDA@mail.gmail.com>
Hello,
On Mon, 10 Jul 2017 16:58:01 +0530, Chakra D wrote:
> Will add the info about mainline
>
> > Also, please put this patch in:
> >
> > board/friendlyarm/nanopi-m1-plus/linux/patches/
I was wrong, it should be the opposite:
board/friendlyarm/nanopi-m1-plus/patches/linux/
> > 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 ?
See above. With BR2_GLOBAL_PATCH_DIR, you need one sub-directory per
package. So, you can do:
BR2_GLOBAL_PATCH_DIR="board/friendlyarm/nanopi-m1-plus/"
with the Linux patch in board/friendlyarm/nanopi-m1-plus/linux
or you can do:
BR2_GLOBAL_PATCH_DIR="board/friendlyarm/nanopi-m1-plus/patches/"
with the Linux patch in board/friendlyarm/nanopi-m1-plus/patches/linux
The latter being the preferred way. See board/beaglebone/ for example.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-07-10 11:35 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 [this message]
2017-07-10 11:41 ` Peter Korsgaard
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=20170710133555.3819183c@windsurf.lan \
--to=thomas.petazzoni@free-electrons.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