From: jason@lakedaemon.net (Jason Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] ARM: mvebu: fixes and improvements for 375 support
Date: Mon, 5 May 2014 12:09:31 -0400 [thread overview]
Message-ID: <20140505160931.GR28159@titan.lakedaemon.net> (raw)
In-Reply-To: <20140505180520.7af699de@skate>
On Mon, May 05, 2014 at 06:05:20PM +0200, Thomas Petazzoni wrote:
> Dear Jason Cooper,
>
> On Mon, 5 May 2014 11:36:54 -0400, Jason Cooper wrote:
>
> > > Thomas Petazzoni (5):
> > > ARM: mvebu: fix thermal quirk SoC revision check
> > > ARM: mvebu: initialize mvebu-soc-id earlier
> > > ARM: mvebu: add Armada 375 A0 revision definition
> > > ARM: mvebu: conditionalize Armada 375 SMP workaround
> > > ARM: mvebu: conditionalize Armada 375 coherency workaround
> >
> > hmmm, I didn't get #5...
>
> Weird because it made it through the LAKML:
> http://lists.infradead.org/pipermail/linux-arm-kernel/2014-May/253251.html
yeah, it was probably a hiccup on my end. Or more specifically, my
inbound remailer. :(
I have it now.
thx,
Jason.
next prev parent reply other threads:[~2014-05-05 16:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 15:05 [PATCH v2 0/5] ARM: mvebu: fixes and improvements for 375 support Thomas Petazzoni
2014-05-05 15:05 ` [PATCH v2 1/5] ARM: mvebu: fix thermal quirk SoC revision check Thomas Petazzoni
2014-05-05 15:05 ` [PATCH v2 2/5] ARM: mvebu: initialize mvebu-soc-id earlier Thomas Petazzoni
2014-05-05 15:05 ` [PATCH v2 3/5] ARM: mvebu: add Armada 375 A0 revision definition Thomas Petazzoni
2014-05-05 15:05 ` [PATCH v2 4/5] ARM: mvebu: conditionalize Armada 375 SMP workaround Thomas Petazzoni
2014-05-05 15:05 ` [PATCH v2 5/5] ARM: mvebu: conditionalize Armada 375 coherency workaround Thomas Petazzoni
2014-05-05 15:36 ` [PATCH v2 0/5] ARM: mvebu: fixes and improvements for 375 support Jason Cooper
2014-05-05 16:05 ` Thomas Petazzoni
2014-05-05 16:09 ` Jason Cooper [this message]
2014-05-08 16:54 ` Jason Cooper
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=20140505160931.GR28159@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=linux-arm-kernel@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