From: Paul Kocialkowski <contact@paulk.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/7] omap-common: Common omap_die_id definition
Date: Tue, 22 Sep 2015 19:11:47 +0200 [thread overview]
Message-ID: <1442941907.2697.0.camel@collins> (raw)
In-Reply-To: <20150922130627.GG26600@bill-the-cat>
Le mardi 22 septembre 2015 ? 09:06 -0400, Tom Rini a ?crit :
> On Sun, Sep 20, 2015 at 12:42:26PM +0200, Paul Kocialkowski wrote:
> > Hi,
> >
> > Le vendredi 04 septembre 2015 ? 14:14 -0400, Tom Rini a ?crit :
> > > On Thu, Aug 27, 2015 at 07:37:08PM +0200, Paul Kocialkowski wrote:
> > >
> > > > This introduces a common definition for omap_die_id, that aims at providing a
> > > > common interface for accessing omap platform's die id bits.
> > > >
> > > > Signed-off-by: Paul Kocialkowski <contact@paulk.fr>
> > >
> > > Reviewed-by: Tom Rini <trini@konsulko.com>
> >
> > These patches have been laying around for some time now, would you agree
> > to merge them?
>
> I think that since this falls under cleanup I'm holding it until the
> next release is out. I took the earlier series so that the 'sniper'
> board works, yes? Thanks!
Sure, that's fine with me, sniper support is there and it doesn't
require these pathces indeed.
Thanks!
--
Paul Kocialkowski, Replicant developer
Replicant is a fully free Android distribution running on several
devices, a free software mobile operating system putting the emphasis on
freedom and privacy/security.
Website: https://www.replicant.us/
Blog: https://blog.replicant.us/
Wiki/tracker/forums: https://redmine.replicant.us/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150922/7ebdf073/attachment.sig>
next prev parent reply other threads:[~2015-09-22 17:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 17:37 [U-Boot] [PATCH 1/7] omap-common: Common omap_die_id definition Paul Kocialkowski
2015-08-27 17:37 ` [U-Boot] [PATCH 2/7] omap3: omap_die_id support Paul Kocialkowski
2015-09-04 18:14 ` Tom Rini
2015-10-22 21:18 ` [U-Boot] [U-Boot,2/7] " Tom Rini
2015-08-27 17:37 ` [U-Boot] [PATCH 3/7] omap4: " Paul Kocialkowski
2015-09-04 18:14 ` Tom Rini
2015-10-22 21:18 ` [U-Boot] [U-Boot,3/7] " Tom Rini
2015-08-27 17:37 ` [U-Boot] [PATCH 4/7] omap5: " Paul Kocialkowski
2015-09-04 18:14 ` Tom Rini
2015-10-22 21:18 ` [U-Boot] [U-Boot,4/7] " Tom Rini
2015-08-27 17:37 ` [U-Boot] [PATCH 5/7] omap-common: Common serial and usbethaddr functions based on die id Paul Kocialkowski
2015-09-04 18:14 ` Tom Rini
2015-10-22 21:19 ` [U-Boot] [U-Boot, " Tom Rini
2015-08-27 17:37 ` [U-Boot] [PATCH 6/7] omap-common: Common function to display die id, replacing omap3-specific version Paul Kocialkowski
2015-09-04 18:14 ` Tom Rini
2015-10-22 21:19 ` [U-Boot] [U-Boot, " Tom Rini
2015-08-27 17:37 ` [U-Boot] [PATCH 7/7] omap-common: Common get_board_serial function to pass serial through ATAG Paul Kocialkowski
2015-09-04 18:14 ` Tom Rini
2015-10-22 21:19 ` [U-Boot] [U-Boot, " Tom Rini
2015-09-03 13:41 ` [U-Boot] [PATCH 1/7] omap-common: Common omap_die_id definition Paul Kocialkowski
2015-09-04 18:14 ` Tom Rini
2015-09-20 10:42 ` Paul Kocialkowski
2015-09-22 13:06 ` Tom Rini
2015-09-22 17:11 ` Paul Kocialkowski [this message]
2015-10-22 21:18 ` [U-Boot] [U-Boot, " Tom Rini
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=1442941907.2697.0.camel@collins \
--to=contact@paulk.fr \
--cc=u-boot@lists.denx.de \
/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