From: andriy.shevchenko@linux.intel.com (Andy Shevchenko)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2 v3] SPI: spi-pxa2xx: Add helpers for regiseters' accessing
Date: Thu, 30 Oct 2014 09:12:14 +0200 [thread overview]
Message-ID: <1414653134.2396.67.camel@linux.intel.com> (raw)
In-Reply-To: <4656BEB6164FC34F8171C6538F1A595B2E9A92B3@SHSMSX101.ccr.corp.intel.com>
On Thu, 2014-10-30 at 01:02 +0000, Chen, Alvin wrote:
> > >
> >
> > Hi Alvin, Weike.
> >
> > I'm not clear if these patches apply to the current tip-of-tree.
> >
> > I thought the action required here, was for a resend of patches to ensure they
> > applied to tip-of-tree ?
> >
> As I said before, it is based on the slave-dma tree (git.infraded.org) for-linus branch, which will be reapplied on top of v3.19-rc1.
>
> That is to say these patches will be applied to slave-dma tree for-linus branch, and then the slave-dma tree for-linus branch will be applied to v3.19.
> Andy, am I right?
All of those patches are in v3.18-rc1, so you may rebase on top of
3.18-rcX safely I guess.
--
Andy Shevchenko <andriy.shevchenko@intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2014-10-30 7:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 15:50 [PATCH 0/2 v3] SPI: spi-pxa2xx: Add support for Intel Quark X1000 SPI controller Weike Chen
2014-10-08 15:50 ` [PATCH 1/2 v3] SPI: spi-pxa2xx: Add helpers for regiseters' accessing Weike Chen
2014-10-29 0:33 ` Chen, Alvin
2014-10-29 11:27 ` Bryan O'Donoghue
2014-10-30 1:02 ` Chen, Alvin
2014-10-30 7:12 ` Andy Shevchenko [this message]
2014-10-31 1:03 ` Chen, Alvin
2014-10-31 5:43 ` Chen, Alvin
2014-11-24 18:59 ` Mark Brown
2014-10-08 15:50 ` [PATCH 2/2 v3] SPI: spi-pxa2xx: SPI support for Intel Quark X1000 Weike Chen
2014-10-09 20:15 ` Bryan O'Donoghue
2014-10-10 0:46 ` Chen, Alvin
2014-10-10 14:10 ` Andy Shevchenko
2014-10-16 0:31 ` [PATCH 0/2 v3] SPI: spi-pxa2xx: Add support for Intel Quark X1000 SPI controller Chen, Alvin
2014-10-16 8:50 ` Mark Brown
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=1414653134.2396.67.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--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;
as well as URLs for NNTP newsgroup(s).