From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/5] board/odroidc2: remove unused files
Date: Wed, 29 Apr 2020 23:23:46 +0200 [thread overview]
Message-ID: <20200429232346.7eed0e36@windsurf.home> (raw)
In-Reply-To: <20200418151020.17197-1-daggs@gmx.com>
On Sat, 18 Apr 2020 18:10:16 +0300
Dagg Stompler <daggs@gmx.com> wrote:
> remove all the odroidc2 board related files.
>
> Signed-off-by: Dagg Stompler <daggs@gmx.com>
> ---
> board/hardkernel/odroidc2/boot.ini | 176 ------------------------
> board/hardkernel/odroidc2/genimage.cfg | 27 ----
> board/hardkernel/odroidc2/post-image.sh | 19 ---
> board/hardkernel/odroidc2/readme.txt | 53 -------
> 4 files changed, 275 deletions(-)
> delete mode 100644 board/hardkernel/odroidc2/boot.ini
> delete mode 100644 board/hardkernel/odroidc2/genimage.cfg
> delete mode 100755 board/hardkernel/odroidc2/post-image.sh
> delete mode 100644 board/hardkernel/odroidc2/readme.txt
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-04-29 21:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-18 15:10 [Buildroot] [PATCH 1/5] board/odroidc2: remove unused files Dagg Stompler
2020-04-18 15:10 ` [Buildroot] [PATCH 2/5] meson-tools: new Package Dagg Stompler
2020-04-18 15:10 ` [Buildroot] [PATCH 3/5] OdroidC2ATF: " Dagg Stompler
2020-04-18 15:10 ` [Buildroot] [PATCH 4/5] board/odroidc2: add board Dagg Stompler
2020-04-18 15:10 ` [Buildroot] [PATCH 5/5] configs/odroidc2: add build config Dagg Stompler
2020-04-29 21:23 ` Thomas Petazzoni [this message]
2020-05-10 18:26 ` [Buildroot] [PATCH 1/5] board/odroidc2: remove unused files 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=20200429232346.7eed0e36@windsurf.home \
--to=thomas.petazzoni@bootlin.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.