From: "Jörg Rödel" <joro@8bytes.org>
To: iommu@lists.linux.dev, Will Deacon <will@kernel.org>,
Jason Gunthorpe <jgg@ziepe.ca>,
Lu Baolu <baolu.lu@linux.intel.com>,
Joerg Roedel <jroedel@suse.de>
Subject: Off for the next two weeks
Date: Fri, 28 Jun 2024 14:48:21 +0200 [thread overview]
Message-ID: <Zn6xFZanlWhN5kw3@8bytes.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 580 bytes --]
Hi,
here is just a short notice that I will be off for the next two weeks.
Will Deacon handles all IOMMU patches during my absence, using our new
joint IOMMU maintainers tree at
git://git.kernel.org/pub/scm/linux/kernel/git/iommu/linux.git
Also note that with the new tree there are a few changes:
* Many branches got renamed to the sheme <vendor>/<iommu-hw>
* Removed some stale branches
* Removed unnecessary iommu/ prefix from branches
* The master branch is now always a merge of latest
'linus/master' with 'next'
See you all in July, have fun!
Regards,
Joerg
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2024-06-28 12:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Zn6xFZanlWhN5kw3@8bytes.org \
--to=joro@8bytes.org \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=jroedel@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox