From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: albert_herranz@yahoo.es, fujita.tomonori@lab.ntt.co.jp,
linux-kernel@vger.kernel.org, jeremy@goop.org,
iommu@lists.linux-foundation.org, linux@arm.linux.org.uk,
dwmw2@infradead.org, chrisw@sous-sol.org,
Ian.Campbell@eu.citrix.com
Subject: Re: [PATCH] swiotlb-0.8.2^H3: seperation of physical/virtual address translation and core memory allocation.
Date: Fri, 4 Jun 2010 16:06:04 -0400 [thread overview]
Message-ID: <20100604200604.GA17645@phenom.dumpdata.com> (raw)
In-Reply-To: <20100604114250.b28f288a.akpm@linux-foundation.org>
> > in your -mm tree.
>
> I don't put individual git trees into -mm any more - I get them from
> linux-next.
Ahh. OK.
>
> I could grab the individual patches but I don't see that this gains
> anyone anything. I'd suggest that you ask Stephen to include this tree
> in linux-next then ask Linus to pull it into 2.6.36-rc1.
Stephen,
I was wondering if you wouldn't mind including the following git tree
in your linux-next?
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/swiotlb-2.6.git
The patches are in the MAIN branch (and also in swiotlb-0.8.3).
They have the Tested-by, Signed-off-by, and Acked-by signatures.
Andrew,
> > [nice description]
Thank you.
>
> The sad thing is that this description will get lost because it isn't
.. snip..
> and then follow it with the specific description for [patch 1/n]. I
> suggest that you make such change in this tree.
Done!
>
> It's not a very good solution because anyone who is looking at [patch
.. snip ..
> "see <patch name> for a description of this work" or similar.
Done!
>
> Even better would be if git understood this workflow - if it was able
> to take commentary-only commits and to bidirectionally link those
> commentaries to the invividual commits which they describe.
>
..snip.
> mixture of "enum dma_data_direction dir" and "enum dma_data_direction
> direction", which could be cleaned up.
Oh, good catch. Fixed that.
next prev parent reply other threads:[~2010-06-04 20:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 17:52 [PATCH] swiotlb-0.8.2: seperation of physical/virtual address translation and core memory allocation Konrad Rzeszutek Wilk
2010-06-04 17:52 ` [PATCH 1/5] swiotlb: add swiotlb_tbl_map_single library function Konrad Rzeszutek Wilk
2010-06-04 17:52 ` [PATCH 2/5] swiotlb: add the swiotlb initialization function with iotlb memory Konrad Rzeszutek Wilk
2010-06-04 17:52 ` [PATCH 3/5] swiotlb: Make internal bookkeeping functions have 'swiotlb_tbl' prefix Konrad Rzeszutek Wilk
2010-06-04 17:52 ` [PATCH 4/5] swiotlb: search and replace "int dir" with "enum dma_data_direction dir" Konrad Rzeszutek Wilk
2010-06-04 17:52 ` [PATCH 5/5] swiotlb: Make swiotlb bookkeeping functions visible in the header file Konrad Rzeszutek Wilk
2010-06-04 18:42 ` [PATCH] swiotlb-0.8.2: seperation of physical/virtual address translation and core memory allocation Andrew Morton
2010-06-04 20:06 ` Konrad Rzeszutek Wilk [this message]
2010-06-05 12:07 ` [PATCH] swiotlb-0.8.2^H3: " Stephen Rothwell
2010-06-07 16:01 ` Konrad Rzeszutek Wilk
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=20100604200604.GA17645@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=akpm@linux-foundation.org \
--cc=albert_herranz@yahoo.es \
--cc=chrisw@sous-sol.org \
--cc=dwmw2@infradead.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=iommu@lists.linux-foundation.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.