[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150819080814.GA18115@lst.de>
Date: Wed, 19 Aug 2015 10:08:14 +0200
From: Christoph Hellwig <hch@....de>
To: Ingo Molnar <mingo@...nel.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Christoph Hellwig <hch@....de>, arnd@...db.de,
linux@....linux.org.uk, catalin.marinas@....com,
will.deacon@....com, ysato@...rs.sourceforge.jp, monstr@...str.eu,
jonas@...thpole.se, cmetcalf@...hip.com, gxt@...c.pku.edu.cn,
x86@...nel.org, linux-alpha@...r.kernel.org,
linux-hexagon@...r.kernel.org, linux-ia64@...r.kernel.org,
linux-mips@...ux-mips.org, linuxppc-dev@...ts.ozlabs.org,
linux-s390@...r.kernel.org, linux-sh@...r.kernel.org,
sparclinux@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: provide more common DMA API functions V2
On Tue, Aug 18, 2015 at 09:51:07AM +0200, Ingo Molnar wrote:
> I.e. shouldn't this be:
>
> > I'll merge these 5 patches for 4.4. That means I'll release them into
> > linux-next after 4.2 is released.
> >
> > [...]
> >
> > Linus will be releasing 4.2 in 1-2 weeks and until then, linux-next is supposed
> > to contain only 4.3 material. Once 4.2 is released and the 4.3 merge window
> > opens, linux-next is open for 4.4 material.
>
> ?
That would make a lot more sense. But also be said as I intended
these as the simple part of the dma work I'd like to get into 4.3.
Andrew, if you think it's not 4.3 material I'd rather keep them in
my git tree for now so that I can stack additional patches I have
in progress on top. A non-git based tree like yours is unfortunately
very bad for patches that are dependencies for others.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists