From: Mika Westerberg <mika.westerberg@intel.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Vinod Koul <vinod.koul@intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.jf.intel.com>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Mika Westerberg <mika.westerberg@linux.jf.intel.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
spear-devel <spear-devel@list.st.com>,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH v3 0/2] dma: support Lynxpoint DMA
Date: Thu, 23 May 2013 14:25:05 +0300 [thread overview]
Message-ID: <20130523112504.GF11878@intel.com> (raw)
In-Reply-To: <CAHp75Vctb1kR8gUQk0vu8scsgjBtZUq9DS0NQ+zVOPAobG0QOw@mail.gmail.com>
On Thu, May 23, 2013 at 02:07:54PM +0300, Andy Shevchenko wrote:
> On Thu, May 23, 2013 at 1:19 PM, Vinod Koul <vinod.koul@intel.com> wrote:
> > On Tue, May 21, 2013 at 12:29:39PM +0300, Andy Shevchenko wrote:
> >> On Tue, 2013-05-14 at 10:24 +0530, Vinod Koul wrote:
> >> > On Wed, May 08, 2013 at 11:55:47AM +0300, Andy Shevchenko wrote:
> >> > > This is the rest of patch series related to ACPI DMA helpers and Lynxpoint DMAC.
> >> > > Patches are rebased against current Linus' tree and Vinod's branch for-linus.
> >> > >
> >> > > Since v2:
> >> > > - remove patches that are already in the Vinod's tree
> >> > > - rebase on top of today's origin/master and Vinod's for-linus branch
> >> > > - fix description in patch 2/2
> >> > Applied both, Thanks
> >>
> >> Thank you for applying them to next.
> >>
> >> I'm just wondering if you are going to send pull request soon to get
> >> them in the v3.10-rcX.
> > Nope these are in next & would show up in Linus's tree in next merge window.
> > Something which is not a bug fix doesnt get merged in rc's. You should know the
> > process
>
> Hmm... Now we have a situation when v3.9.x has support of Lynxpoint
> DMA, v3.10-rc2 has it broken.
> As far as I remember our discussion [1] we agreed to wait for
> v3.10-rc1 due to merge of linux-pm patches.
Yes, and we need that stuff for BayTrail support as well. Currently Rafael
is waiting these patches so that he can then merge [1].
[1] https://lkml.org/lkml/2013/5/13/542
next prev parent reply other threads:[~2013-05-23 11:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 8:55 [PATCH v3 0/2] dma: support Lynxpoint DMA Andy Shevchenko
2013-05-08 8:55 ` [PATCH v3 1/2] dma: acpi-dma: parse CSRT to extract additional resources Andy Shevchenko
2013-05-08 8:55 ` [PATCH v3 2/2] ACPI / LPSS: register clock device for Lynxpoint DMA properly Andy Shevchenko
2013-05-14 4:54 ` [PATCH v3 0/2] dma: support Lynxpoint DMA Vinod Koul
2013-05-21 9:29 ` Andy Shevchenko
2013-05-23 10:19 ` Vinod Koul
2013-05-23 11:07 ` Andy Shevchenko
2013-05-23 11:25 ` Mika Westerberg [this message]
2013-05-23 16:22 ` Vinod Koul
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=20130523112504.GF11878@intel.com \
--to=mika.westerberg@intel.com \
--cc=andriy.shevchenko@linux.jf.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.jf.intel.com \
--cc=rafael.j.wysocki@intel.com \
--cc=spear-devel@list.st.com \
--cc=vinod.koul@intel.com \
--cc=viresh.kumar@linaro.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).