From: Chuck Lever III <chuck.lever@oracle.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Chuck Lever <cel@kernel.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Robin Murphy <robin.murphy@arm.com>,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>
Subject: Re: [PATCH RFC 1/9] dma-debug: Fix a typo in a debugging eye-catcher
Date: Fri, 20 Oct 2023 13:38:01 +0000 [thread overview]
Message-ID: <D983E311-0357-454C-8FA8-D365536C5ADB@oracle.com> (raw)
In-Reply-To: <20231020044941.GA12234@lst.de>
> On Oct 20, 2023, at 12:49 AM, Christoph Hellwig <hch@lst.de> wrote:
>
> Thanks,
>
> I'll add this to the dma-mapping tree.
>
> FYI, I only got patches 1, 2 and the cover letter. Something seems to
> be broken in your mailer setup.
I think you were explicitly copied only the first two.
I assumed you would see the others on the mailing lists.
I used information in MAINTAINERS for the files and
subsystems those patches modified. Is that information
up to date?
--
Chuck Lever
next prev parent reply other threads:[~2023-10-20 13:38 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 15:25 [PATCH RFC 0/9] Exploring biovec support in (R)DMA API Chuck Lever
2023-10-19 15:25 ` Chuck Lever
2023-10-19 15:25 ` [PATCH RFC 1/9] dma-debug: Fix a typo in a debugging eye-catcher Chuck Lever
2023-10-20 4:49 ` Christoph Hellwig
2023-10-20 13:38 ` Chuck Lever III [this message]
2023-10-23 5:56 ` Christoph Hellwig
2023-10-19 15:25 ` [PATCH RFC 2/9] bvec: Add bio_vec fields to manage DMA mapping Chuck Lever
2023-10-19 15:25 ` Chuck Lever
2023-10-19 15:25 ` [PATCH RFC 3/9] dma-debug: Add dma_debug_ helpers for mapping bio_vec arrays Chuck Lever
2023-10-19 15:25 ` Chuck Lever
2023-10-19 21:38 ` kernel test robot
2023-10-19 23:21 ` Chuck Lever III
2023-10-23 2:43 ` Liu, Yujie
2023-10-23 14:27 ` Chuck Lever III
2023-10-19 21:49 ` kernel test robot
2023-10-19 15:25 ` [PATCH RFC 4/9] mm: kmsan: Add support for DMA " Chuck Lever
2023-10-19 15:25 ` Chuck Lever
2023-10-19 15:26 ` [PATCH RFC 5/9] dma-direct: Support direct " Chuck Lever
2023-10-19 15:26 ` Chuck Lever
2023-10-19 15:26 ` [PATCH RFC 6/9] DMA-API: Add dma_sync_bvecs_for_cpu() and dma_sync_bvecs_for_device() Chuck Lever
2023-10-19 15:26 ` Chuck Lever
2023-10-19 15:26 ` [PATCH RFC 7/9] DMA: Add dma_map_bvecs_attrs() Chuck Lever
2023-10-19 15:26 ` Chuck Lever
2023-10-19 22:10 ` kernel test robot
2023-10-19 15:26 ` [PATCH RFC 8/9] iommu/dma: Support DMA-mapping a bio_vec array Chuck Lever
2023-10-19 15:26 ` Chuck Lever
2023-10-19 15:26 ` [PATCH RFC 9/9] RDMA: Add helpers for DMA-mapping an array of bio_vecs Chuck Lever
2023-10-19 15:26 ` Chuck Lever
2023-10-19 15:53 ` [PATCH RFC 0/9] Exploring biovec support in (R)DMA API Matthew Wilcox
2023-10-19 17:48 ` Chuck Lever
2023-10-20 4:58 ` Christoph Hellwig
2023-10-20 10:30 ` Robin Murphy
2023-10-23 5:59 ` Christoph Hellwig
2023-10-19 16:43 ` Robin Murphy
2023-10-19 17:53 ` Jason Gunthorpe
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=D983E311-0357-454C-8FA8-D365536C5ADB@oracle.com \
--to=chuck.lever@oracle.com \
--cc=cel@kernel.org \
--cc=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=m.szyprowski@samsung.com \
--cc=robin.murphy@arm.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 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.