From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/9] package/rcw: upgrade the rcw version to LSDK-19.09
Date: Wed, 20 Nov 2019 10:32:04 +0100 [thread overview]
Message-ID: <20191120103204.19a15798@windsurf.home> (raw)
In-Reply-To: <8ef6b0156f54102d837ecfc429ae810d@walle.cc>
Hello,
On Wed, 20 Nov 2019 10:21:12 +0100
Michael Walle <michael@walle.cc> wrote:
> > diff --git a/package/rcw/rcw.hash b/package/rcw/rcw.hash
> > index 7de1ec659a..3fbb5d167f 100644
> > --- a/package/rcw/rcw.hash
> > +++ b/package/rcw/rcw.hash
>
> sorry for missing the initial commit.. but IMHO the package name "rcw"
> is _really_ bad. because its too generic. what if another SoC also has a
> package rcw. So if it is still possible, could it be renamed to
> rcw-qoriq ?
True, rcw is very short and quite generic. Matt, what do you think?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-11-20 9:32 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 4:07 [Buildroot] [PATCH 0/9] new board ls1028ardb introduced Changming Huang
2019-11-20 4:07 ` [Buildroot] [PATCH 1/9] package/rcw: upgrade the rcw version to LSDK-19.09 Changming Huang
2019-11-20 7:59 ` Thomas Petazzoni
2019-11-20 8:04 ` [Buildroot] [EXT] " Jerry Huang
2019-11-20 9:21 ` [Buildroot] " Michael Walle
2019-11-20 9:32 ` Thomas Petazzoni [this message]
2019-11-20 9:38 ` Matthew Weber
2019-11-20 9:45 ` Thomas Petazzoni
2019-11-20 9:51 ` [Buildroot] [External] " Matthew Weber
2019-11-20 9:57 ` [Buildroot] [EXT] " Jerry Huang
2019-11-20 10:00 ` [Buildroot] " Michael Walle
2019-11-20 10:23 ` Matthew Weber
2019-11-20 9:54 ` [Buildroot] [EXT] " Jerry Huang
2019-11-20 4:07 ` [Buildroot] [PATCH 2/9] package/rcw: add target rcw binary support Changming Huang
2019-11-20 9:30 ` Matthew Weber
2019-11-20 4:07 ` [Buildroot] [PATCH 3/9] boot/arm-trusted-firmware: Add u-boot-dtb.bin support Changming Huang
2019-11-20 7:37 ` Sergey Matyukevich
2019-11-20 8:13 ` [Buildroot] [EXT] " Jerry Huang
2019-11-20 9:07 ` [Buildroot] " Thomas Petazzoni
2019-11-20 4:07 ` [Buildroot] [PATCH 4/9] boot/arm-trusted-firmware: Add RCW support Changming Huang
2019-11-20 7:50 ` Sergey Matyukevich
2019-11-20 8:45 ` [Buildroot] [EXT] " Jerry Huang
2019-11-21 8:02 ` Sergey Matyukevich
2019-11-21 8:37 ` Jerry Huang
2019-11-21 8:39 ` Jerry Huang
2019-11-20 4:07 ` [Buildroot] [PATCH 5/9] package/freescale-qoriq: new package directory Changming Huang
2019-11-20 8:57 ` Thomas Petazzoni
2019-11-20 4:07 ` [Buildroot] [PATCH 6/9] package/freescale-qoriq/cadence: new package Changming Huang
2019-11-20 9:13 ` Thomas Petazzoni
2019-11-20 9:30 ` [Buildroot] [EXT] " Jerry Huang
2019-11-20 9:36 ` Thomas Petazzoni
2019-11-20 9:47 ` Jerry Huang
2019-11-20 4:07 ` [Buildroot] [PATCH 7/9] package/rcw: Enable IIC5_PMUX and CLK_OUT_PMUX for GPIO Changming Huang
2019-11-20 9:14 ` Thomas Petazzoni
2019-11-20 9:34 ` [Buildroot] [EXT] " Jerry Huang
2019-11-20 9:38 ` Thomas Petazzoni
2019-11-20 10:22 ` Jerry Huang
2019-11-20 4:07 ` [Buildroot] [PATCH 8/9] board/freescale/common/ls: Add standard post image script for Layerscape processors Changming Huang
2019-11-20 4:07 ` [Buildroot] [PATCH 9/9] configs/freescale_ls1028ardb*: new board Changming Huang
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=20191120103204.19a15798@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.