From: Christoph Hellwig <hch@lst.de>
To: Ingo Molnar <mingo@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Christoph Hellwig <hch@lst.de>,
arnd@arndb.de, linux@arm.linux.org.uk, catalin.marinas@arm.com,
will.deacon@arm.com, ysato@users.sourceforge.jp,
monstr@monstr.eu, jonas@southpole.se, cmetcalf@ezchip.com,
gxt@mprc.pku.edu.cn, x86@kernel.org, linux-alpha@vger.kernel.org,
linux-hexagon@vger.kernel.org, linux-ia64@vger.kernel.org,
linux-mips@linux-mips.org, linuxppc-dev@lists.ozlabs.org,
linux-s390@vger.kernel.org, linux-sh@vger.kernel.org,
sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: provide more common DMA API functions V2
Date: Wed, 19 Aug 2015 10:08:14 +0200 [thread overview]
Message-ID: <20150819080814.GA18115@lst.de> (raw)
In-Reply-To: <20150818075107.GA31884@gmail.com>
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.
next prev parent reply other threads:[~2015-08-19 8:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 7:06 provide more common DMA API functions V2 Christoph Hellwig
2015-08-17 7:06 ` [PATCH 1/5] dma-mapping: consolidate dma_{alloc, free}_{attrs, coherent} Christoph Hellwig
2015-08-17 7:06 ` [PATCH 2/5] dma-mapping: consolidate dma_{alloc,free}_noncoherent Christoph Hellwig
2015-08-17 7:06 ` [PATCH 3/5] dma-mapping: cosolidate dma_mapping_error Christoph Hellwig
2015-08-27 13:49 ` Andy Shevchenko
2015-08-17 7:06 ` [PATCH 4/5] dma-mapping: consolidate dma_supported Christoph Hellwig
2015-08-17 7:06 ` [PATCH 5/5] dma-mapping: consolidate dma_set_mask Christoph Hellwig
2015-08-17 21:24 ` provide more common DMA API functions V2 Andrew Morton
2015-08-18 5:38 ` Christoph Hellwig
2015-08-18 5:45 ` Andrew Morton
2015-08-18 5:53 ` Christoph Hellwig
2015-08-18 6:07 ` Stephen Rothwell
2015-08-18 7:51 ` Ingo Molnar
2015-08-19 8:08 ` Christoph Hellwig [this message]
2015-08-19 21:36 ` Andrew Morton
2015-08-19 23:52 ` Stephen Rothwell
2015-08-20 1:09 ` Michael Ellerman
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=20150819080814.GA18115@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=cmetcalf@ezchip.com \
--cc=gxt@mprc.pku.edu.cn \
--cc=jonas@southpole.se \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@kernel.org \
--cc=monstr@monstr.eu \
--cc=sparclinux@vger.kernel.org \
--cc=will.deacon@arm.com \
--cc=x86@kernel.org \
--cc=ysato@users.sourceforge.jp \
/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).