From: "Chen, Alvin" <alvin.chen@intel.com>
To: Bryan O'Donoghue <pure.logic@nexus-software.ie>,
Eric Miao <eric.y.miao@gmail.com>,
Russell King <linux@arm.linux.org.uk>,
"Haojian Zhuang" <haojian.zhuang@gmail.com>,
Mark Brown <broonie@kernel.org>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Westerberg, Mika" <mika.westerberg@intel.com>,
"Kweh, Hock Leong" <hock.leong.kweh@intel.com>,
"Ong, Boon Leong" <boon.leong.ong@intel.com>,
"Tan, Raymond" <raymond.tan@intel.com>
Subject: RE: [PATCH 1/2 v3] SPI: spi-pxa2xx: Add helpers for regiseters' accessing
Date: Thu, 30 Oct 2014 01:02:16 +0000 [thread overview]
Message-ID: <4656BEB6164FC34F8171C6538F1A595B2E9A92B3@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <5450CF36.7060105@nexus-software.ie>
> >
>
> 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?
next prev parent reply other threads:[~2014-10-30 1:02 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
[not found] ` <1412783423-9408-2-git-send-email-alvin.chen-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-10-29 0:33 ` Chen, Alvin
[not found] ` <4656BEB6164FC34F8171C6538F1A595B2E9A90E6-0J0gbvR4kThpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-10-29 11:27 ` Bryan O'Donoghue
2014-10-30 1:02 ` Chen, Alvin [this message]
[not found] ` <4656BEB6164FC34F8171C6538F1A595B2E9A92B3-0J0gbvR4kThpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-10-30 7:12 ` Andy Shevchenko
[not found] ` <1414653134.2396.67.camel-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
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
[not found] ` <5436ECC6.9080704-SyKdqv6vbfZdzvEItQ6vdLNAH6kLmebB@public.gmane.org>
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
[not found] ` <4656BEB6164FC34F8171C6538F1A595B2E999534-0J0gbvR4kThpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
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=4656BEB6164FC34F8171C6538F1A595B2E9A92B3@SHSMSX101.ccr.corp.intel.com \
--to=alvin.chen@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=boon.leong.ong@intel.com \
--cc=broonie@kernel.org \
--cc=eric.y.miao@gmail.com \
--cc=haojian.zhuang@gmail.com \
--cc=hock.leong.kweh@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mika.westerberg@intel.com \
--cc=pure.logic@nexus-software.ie \
--cc=raymond.tan@intel.com \
/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).