From: trini@konsulko.com (Tom Rini)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH v2 0/2] Prepare U-Boot for more Amlogic boards
Date: Fri, 24 Jun 2016 17:11:10 -0400 [thread overview]
Message-ID: <20160624211110.GG19080@bill-the-cat> (raw)
In-Reply-To: <20160624210103.GA5083@localhost>
On Fri, Jun 24, 2016 at 11:01:03PM +0200, Carlo Caione wrote:
> On 10/06/16 20:18, Carlo Caione wrote:
> > From: Carlo Caione <carlo@endlessm.com>
> >
> > Refactor the Odroid-C2 support code to prepare U-Boot for more Amlogic board
> > submissions.
> > The goal is to reduce the redundancy of the configuration files and unify all
> > the board support files onto a single amlogic directory.
> >
> > Changelog:
> > v2:
> > - Added Reviewed-by
> > - Now 2/2 clearly shows the renaming
>
> What's left for this patchset? I have a couple of submissions depending
> on this one.
Sorry for the delay, working on this shortly.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-amlogic/attachments/20160624/71992a29/attachment.sig>
prev parent reply other threads:[~2016-06-24 21:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-10 18:18 [PATCH v2 0/2] Prepare U-Boot for more Amlogic boards Carlo Caione
2016-06-10 18:18 ` [PATCH v2 1/2] configs: gxbb: Introduce a common config header file Carlo Caione
2016-06-12 21:03 ` Beniamino Galvani
2016-06-25 2:51 ` [U-Boot,v2,1/2] " Tom Rini
2016-06-10 18:18 ` [PATCH v2 2/2] board: amlogic: Rename folder for Amlogic boards Carlo Caione
2016-06-12 21:05 ` Beniamino Galvani
2016-06-25 2:52 ` [U-Boot,v2,2/2] " Tom Rini
2016-06-24 21:01 ` [PATCH v2 0/2] Prepare U-Boot for more " Carlo Caione
2016-06-24 21:11 ` Tom Rini [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=20160624211110.GG19080@bill-the-cat \
--to=trini@konsulko.com \
--cc=linus-amlogic@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).