From: Ingo Molnar <mingo@elte.hu>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: tony.luck@intel.com, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org, Yasunori Goto <y-goto@jp.fujitsu.com>
Subject: Re: [PATCH -tip 1/3] IA64: fix swiotlb alloc_coherent for non
Date: Thu, 29 Jan 2009 13:40:22 +0000 [thread overview]
Message-ID: <20090129134022.GG24391@elte.hu> (raw)
In-Reply-To: <1233147198-30299-1-git-send-email-fujita.tomonori@lab.ntt.co.jp>
Applied them to tip:core/iommu:
d7ab5c4: intel-iommu: make dma mapping functions static
dfb805e: IA64: fix VT-d dma_mapping_error
97d9800: IA64: fix swiotlb alloc_coherent for non DMA_64BIT_MASK devices
thanks!
Ingo
prev parent reply other threads:[~2009-01-29 13:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-28 12:53 [PATCH -tip 1/3] IA64: fix swiotlb alloc_coherent for non DMA_64BIT_MASK devices FUJITA Tomonori
2009-01-28 12:53 ` [PATCH -tip 2/3] IA64: fix VT-d dma_mapping_error FUJITA Tomonori
2009-01-28 12:53 ` [PATCH -tip 3/3] intel-iommu: make dma mapping functions static FUJITA Tomonori
2009-01-29 11:41 ` [PATCH -tip 1/3] IA64: fix swiotlb alloc_coherent for non DMA_64BIT_MASK devices Yasunori Goto
2009-01-29 11:54 ` [PATCH -tip 1/3] IA64: fix swiotlb alloc_coherent for non FUJITA Tomonori
2009-01-29 22:54 ` [PATCH -tip 1/3] IA64: fix swiotlb alloc_coherent for non DMA_64BIT_MASK devices Yasunori Goto
2009-01-29 23:36 ` [PATCH -tip 1/3] IA64: fix swiotlb alloc_coherent for non FUJITA Tomonori
2009-01-30 11:24 ` [PATCH -tip 1/3] IA64: fix swiotlb alloc_coherent for non DMA_64BIT_MASK devices Yasunori Goto
2009-02-02 23:28 ` [PATCH -tip 1/3] IA64: fix swiotlb alloc_coherent for non FUJITA Tomonori
2009-02-03 1:52 ` [PATCH -tip 1/3] IA64: fix swiotlb alloc_coherent for non DMA_64BIT_MASK devices Yasunori Goto
2009-01-29 13:40 ` Ingo Molnar [this message]
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=20090129134022.GG24391@elte.hu \
--to=mingo@elte.hu \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
--cc=y-goto@jp.fujitsu.com \
/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