iommu.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Marek Szyprowski <m.szyprowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
To: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>,
	Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: mailing list for the dma mapping code
Date: Mon, 31 Jul 2017 07:42:05 +0200	[thread overview]
Message-ID: <b35dfcb6-cafc-788e-93fb-bd23b7f1a815@samsung.com> (raw)
In-Reply-To: <20170717064526.GA15839-jcswGhMUV9g@public.gmane.org>

Hi All,

On 2017-07-17 08:45, Christoph Hellwig wrote:
> Hi all,
>
> currently the dma-mapping code doesn't have a dedicated mailing list,
> and thus posts get lots on linux-kernel.  I wonder if we should add
> a new separate list for it, or if it makes sense to reuse the existing
> iommu list given that there is a fair amount of overlap.

I don't think that having one more mailing list is really needed. IOMMU
ml is fine for me if its current users are not against using also for
generic DMA-mapping related talks.

Best regards
-- 
Marek Szyprowski, PhD
Samsung R&D Institute Poland

      parent reply	other threads:[~2017-07-31  5:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170717064530epcas1p420482d9baffc1fdfabcc674dd351f7bd@epcas1p4.samsung.com>
2017-07-17  6:45 ` mailing list for the dma mapping code Christoph Hellwig
     [not found]   ` <20170717064526.GA15839-jcswGhMUV9g@public.gmane.org>
2017-07-31  5:42     ` Marek Szyprowski [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=b35dfcb6-cafc-788e-93fb-bd23b7f1a815@samsung.com \
    --to=m.szyprowski-sze3o3uu22jbdgjk7y7tuq@public.gmane.org \
    --cc=hch-jcswGhMUV9g@public.gmane.org \
    --cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=robin.murphy-5wv7dgnIgG8@public.gmane.org \
    /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).