From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Added support for LeMaker Banana Pi M2 Plus board.
Date: Tue, 22 Aug 2017 23:04:41 +0200 [thread overview]
Message-ID: <20170822230441.3a5ff8ea@windsurf> (raw)
In-Reply-To: <1503433993-131060-1-git-send-email-mike.harmony@snapav.com>
Hello,
Thanks for your contribution!
On Tue, 22 Aug 2017 16:33:13 -0400, mike.harmony at snapav.com wrote:
> From: Mike Harmony <mike.harmony@houselogix.com>
>
> Signed-off-by: Mike Harmony <mike.harmony@houselogix.com>
> ---
> board/lemaker/m2-plus/boot.cmd | 7 +
> board/lemaker/m2-plus/genimage.cfg | 33 +
> board/lemaker/m2-plus/post-build.sh | 12 +
> configs/bananapi_m2_plus_defconfig | 3280 +++++++++++++++++++++++++++++++++++
> 4 files changed, 3332 insertions(+)
> create mode 100644 board/lemaker/m2-plus/boot.cmd
> create mode 100644 board/lemaker/m2-plus/genimage.cfg
> create mode 100755 board/lemaker/m2-plus/post-build.sh
> create mode 100644 configs/bananapi_m2_plus_defconfig
I haven't looked in details at your submission. However, we already had
a contribution adding support for Banana Pi M2 Plus, see:
Subject: [Buildroot] [PATCH v2 2/3] Board: Add Bananapi M2 Plus support
Date: Sun, 18 Jun 2017 22:18:02 +0530
It was not merged because I had some comments, and the original
submitter didn't send an updated version.
Regarding your submission, at the very least:
- The defconfig should be generated with "make savedefconfig", to be a
minimal defconfig. Look at other defconfig files in configs/
- Add yourself to the DEVELOPERS file
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-08-22 21:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 20:33 [Buildroot] [PATCH 1/1] Added support for LeMaker Banana Pi M2 Plus board mike.harmony at snapav.com
2017-08-22 21:04 ` Thomas Petazzoni [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=20170822230441.3a5ff8ea@windsurf \
--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