From: Christoph Hellwig <hch@infradead.org>
To: Joerg Roedel <joro@8bytes.org>
Cc: Joerg Roedel <jroedel@suse.de>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, Christoph Hellwig <hch@infradead.org>,
iommu@lists.linux-foundation.org
Subject: Re: [PATCH v2] MAINTAINERS: Add new IOMMU development mailing list
Date: Fri, 24 Jun 2022 05:59:39 -0700 [thread overview]
Message-ID: <YrW1Oy0ojM5pXREB@infradead.org> (raw)
In-Reply-To: <20220624125139.412-1-joro@8bytes.org>
On Fri, Jun 24, 2022 at 02:51:39PM +0200, Joerg Roedel wrote:
> From: Joerg Roedel <jroedel@suse.de>
>
> The IOMMU mailing list will move from lists.linux-foundation.org to
> lists.linux.dev. The hard switch of the archive will happen on July
> 5th, but add the new list now already so that people start using the
> list when sending patches. After July 5th the old list will disappear.
Shouldn't this also remove the old list given it has only a few days
to live?
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Joerg Roedel <joro@8bytes.org>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
iommu@lists.linux.dev, Joerg Roedel <jroedel@suse.de>,
Christoph Hellwig <hch@infradead.org>,
stable@vger.kernel.org
Subject: Re: [PATCH v2] MAINTAINERS: Add new IOMMU development mailing list
Date: Fri, 24 Jun 2022 05:59:39 -0700 [thread overview]
Message-ID: <YrW1Oy0ojM5pXREB@infradead.org> (raw)
Message-ID: <20220624125939.4LLI0l7n_ubNbWJe6ufMY0G72eD1uvSAXsL1UTtcvg8@z> (raw)
In-Reply-To: <20220624125139.412-1-joro@8bytes.org>
On Fri, Jun 24, 2022 at 02:51:39PM +0200, Joerg Roedel wrote:
> From: Joerg Roedel <jroedel@suse.de>
>
> The IOMMU mailing list will move from lists.linux-foundation.org to
> lists.linux.dev. The hard switch of the archive will happen on July
> 5th, but add the new list now already so that people start using the
> list when sending patches. After July 5th the old list will disappear.
Shouldn't this also remove the old list given it has only a few days
to live?
next prev parent reply other threads:[~2022-06-24 12:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 12:51 [PATCH v2] MAINTAINERS: Add new IOMMU development mailing list Joerg Roedel
2022-06-24 12:51 ` Joerg Roedel
2022-06-24 12:59 ` Christoph Hellwig [this message]
2022-06-24 12:59 ` Christoph Hellwig
2022-06-24 13:20 ` Joerg Roedel
2022-06-24 13:20 ` Joerg Roedel
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=YrW1Oy0ojM5pXREB@infradead.org \
--to=hch@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox