From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Francois Perrad <fperrad@gmail.com>
Cc: buildroot@busybox.net
Subject: Re: [Buildroot] [PATCH v3] board/olimex/stmp1_olinuxino: add STMP157-OLinuXino-LIME2 board support
Date: Sun, 26 Dec 2021 23:42:29 +0100 [thread overview]
Message-ID: <20211226234229.52fbd54e@windsurf> (raw)
In-Reply-To: <20211218090420.311210-1-francois.perrad@gadz.org>
On Sat, 18 Dec 2021 10:04:20 +0100
Francois Perrad <fperrad@gmail.com> wrote:
> kernel & uboot come from Olimex forks
>
> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
> ---
> board/olimex/stmp1_olinuxino/genimage.cfg | 25 ++++
> board/olimex/stmp1_olinuxino/linux.config | 125 ++++++++++++++++++
> board/olimex/stmp1_olinuxino/readme.txt | 53 ++++++++
> .../boot/extlinux/extlinux.conf | 4 +
> .../olimex_stmp157_olinuxino_lime_defconfig | 47 +++++++
> 5 files changed, 254 insertions(+)
> create mode 100644 board/olimex/stmp1_olinuxino/genimage.cfg
> create mode 100644 board/olimex/stmp1_olinuxino/linux.config
> create mode 100644 board/olimex/stmp1_olinuxino/readme.txt
> create mode 100644 board/olimex/stmp1_olinuxino/rootfs_overlay/boot/extlinux/extlinux.conf
> create mode 100644 configs/olimex_stmp157_olinuxino_lime_defconfig
You had forgotten to add entries in the DEVELOPERS, so I've done that
and applied. Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2021-12-26 22:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-18 9:04 [Buildroot] [PATCH v3] board/olimex/stmp1_olinuxino: add STMP157-OLinuXino-LIME2 board support Francois Perrad
2021-12-26 22:42 ` 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=20211226234229.52fbd54e@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
--cc=fperrad@gmail.com \
/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