All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Rödel" <joro@8bytes.org>
To: iommu@lists.linux-foundation.org
Cc: robin.murphy@arm.com,
	Alex Williamson <alex.williamson@redhat.com>,
	Will Deacon <will@kernel.org>, Jason Gunthorpe <jgg@nvidia.com>
Subject: Re: New IOMMU mailing list coming
Date: Fri, 1 Jul 2022 14:16:22 +0200	[thread overview]
Message-ID: <Yr7lluiS4tz4HPTE@8bytes.org> (raw)
In-Reply-To: <YqhHHBkvGL74azMg@8bytes.org>

On Tue, Jun 14, 2022 at 10:30:21AM +0200, Jörg Rödel wrote:
> Hi all,
> 
> after several problems with the current IOMMU mailing list (no DKIM
> support, poor b4 interoperability) we have decided to move the IOMMU
> development discussions to a new list hosted at lists.linux.dev.
> 
> The new list is up and running already, to subscribe please send an
> email to iommu+subscribe@lists.linux.dev. It is not yet archived, but
> there will be a hard switch between the old and the new list on
> 
> 	July 5th, 2022
> 
> After that date the old list will no longer work and the archive will
> switch to the new mailing list.
> 
> Sorry for any inconveniences this might cause.

Gentle reminder that the old IOMMU mailing list at
	iommu@lists.linux-foundation.org
	
will no longer be archived from Tuesday, July 5th on and will disappear
soon after. If not already done, please subscribe to the new mailing
list at

	iomm+subscribe@lists.linux.dev

Thanks and see you over there!


	Joerg
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

      parent reply	other threads:[~2022-07-01 12:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-14  8:30 New IOMMU mailing list coming Jörg Rödel
2022-06-23 14:57 ` Jason Gunthorpe via iommu
2022-07-01 12:16 ` Jörg Rödel [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=Yr7lluiS4tz4HPTE@8bytes.org \
    --to=joro@8bytes.org \
    --cc=alex.williamson@redhat.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jgg@nvidia.com \
    --cc=robin.murphy@arm.com \
    --cc=will@kernel.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 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.