Re: [PATCH v3 0/2] dma: support Lynxpoint DMA

[Vinod Koul]

On Thu, May 23, 2013 at 02:25:05PM +0300, Mika Westerberg wrote:
> 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@xxxxxxxxx> 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.
How does it work in 3.9 and not in 3.10?

> > As far as I remember our discussion [1]  we agreed to wait for
> > v3.10-rc1 due to merge of linux-pm patches.
Yes I applied these. BUT that does not mean they will get merged to Linus as
this is not a fix. Which part is not obvious here. This is _the_ process.

> Yes, and we need that stuff for BayTrail support as well. Currently Rafael
> is waiting these patches so that he can then merge [1].
I can keep these in a topic/branch which wont eb rebased. So Rafael can merge
the other dependecies. Let me know if you would like that.

--
~Vinod
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/