From: Kumar Gala <galak@kernel.crashing.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
beckyb@kernel.crashing.org, linux-kernel@vger.kernel.org,
jeremy@goop.org, ian.campbell@citrix.com
Subject: Re: [PATCH 5/7] swiotlb: (re)Create swiotlb_unmap_single
Date: Wed, 8 Apr 2009 08:35:39 -0500 [thread overview]
Message-ID: <C650C751-B5D8-4FA5-87E1-CF20D596F3B7@kernel.crashing.org> (raw)
In-Reply-To: <20090408124322.GG18581@elte.hu>
On Apr 8, 2009, at 7:43 AM, Ingo Molnar wrote:
>
> * FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> wrote:
>
>>> Same here. It makes it easier for us to work on the powerpc arch
>>> specific changes for .31 if we can get these into .30. What are you
>>> looking at for .31?
>>
>> I need to finish the dma_mapping_ops cleanups and cross-arch
>> unification stuff:
>>
>> http://marc.info/?l=linux-kernel&m=123827903216314&w=2
>>
>> But the changes to swiotlb is minor. BTW, I have the patches for
>> powerpc too.
>>
>>> Ingo, any comments on that?
>
> if it's genuine fixes we can do it post-rc1, but it looks a tad wide
> for that:
>
> arch/x86/kernel/pci-swiotlb.c | 2 +-
> include/linux/swiotlb.h | 3 +-
> lib/swiotlb.c | 115 +++++++++++++++++++++
> +-------------------
>
> the patches came right in the merge window - that's too late for
> IOMMU bits, the patch cutoff is generally the beginning of the merge
> window. (Which was on March 23 in this window)
Fair.
> But i can queue them up in the .31 queue if it has all the Acks from
> you folks. Becky, mind resending the latest version, with all the
> acks in place?
I can do this in Becky's abscense this week. The only "acks" I've
seen are from FUJITA Tomonori.
Can we ask there be a unique swiotlb branch in your tree to make it
easier for us to continue additional swiotlb work as well as arch
specific work.
- k
next prev parent reply other threads:[~2009-04-08 13:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-04 1:56 [PATCH V2 0/7] swiotlb: changes for powerpc/highmem Becky Bruce
2009-04-04 1:56 ` [PATCH 1/7] swiotlb: comment corrections (no code changes) Becky Bruce
2009-04-04 1:56 ` [PATCH 2/7] swiotlb: fix compile warning Becky Bruce
2009-04-04 1:56 ` [PATCH 3/7] swiotlb: map_page fix for highmem systems Becky Bruce
2009-04-04 1:56 ` [PATCH 4/7] swiotlb: Allow arch override of address_needs_mapping Becky Bruce
2009-04-04 1:56 ` [PATCH 5/7] swiotlb: (re)Create swiotlb_unmap_single Becky Bruce
2009-04-04 1:56 ` [PATCH 6/7] swiotlb: Use swiotlb_sync_single instead of duplicating code Becky Bruce
2009-04-04 1:56 ` [PATCH 7/7] swiotlb: Change swiotlb_bus_to[phys,virt] prototypes Becky Bruce
2009-04-07 2:24 ` [PATCH 5/7] swiotlb: (re)Create swiotlb_unmap_single FUJITA Tomonori
2009-04-07 6:34 ` Kumar Gala
2009-04-07 9:09 ` FUJITA Tomonori
2009-04-07 15:32 ` Kumar Gala
2009-04-07 16:37 ` FUJITA Tomonori
2009-04-07 16:50 ` Kumar Gala
2009-04-07 17:22 ` FUJITA Tomonori
2009-04-07 17:32 ` Kumar Gala
2009-04-07 18:18 ` FUJITA Tomonori
2009-04-08 12:43 ` Ingo Molnar
2009-04-08 13:35 ` Kumar Gala [this message]
2009-04-08 14:05 ` Ingo Molnar
2009-04-08 14:10 ` Kumar Gala
2009-04-07 2:24 ` [PATCH V2 0/7] swiotlb: changes for powerpc/highmem FUJITA Tomonori
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=C650C751-B5D8-4FA5-87E1-CF20D596F3B7@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=beckyb@kernel.crashing.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=ian.campbell@citrix.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®