Linux IOMMU Development
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Baolu Lu <baolu.lu@linux.intel.com>
Cc: "Jörg Rödel" <joro@8bytes.org>,
	iommu@lists.linux.dev, "Robin Murphy" <robin.murphy@arm.com>,
	"Jason Gunthorpe" <jgg@nvidia.com>
Subject: Re: Off for two weeks
Date: Mon, 14 Jul 2025 11:00:47 +0100	[thread overview]
Message-ID: <aHTVT4SEEyZmDdIO@willie-the-truck> (raw)
In-Reply-To: <551c46fd-d034-4b06-94a6-6080dc9b9600@linux.intel.com>

On Mon, Jul 14, 2025 at 01:12:38PM +0800, Baolu Lu wrote:
> On 7/12/25 00:14, Will Deacon wrote:
> > On Fri, Jul 11, 2025 at 04:39:46PM +0200, Jörg Rödel wrote:
> > > Just a note that I will be out for the next two weeks and not do any updates to
> > > the IOMMU tree.
> > 
> > Have a good break, Joerg!
> > 
> > > Will Deacon thankfully takes over during this time, so please
> > > send everything his way :) I will be back on July 28th.
> > 
> > I'll do a sweep of the list and pick up what I spot but if folks think
> > that I may have missed something, please just shout. I'll switch to
> > "fixes only" mode middle of next week, given where we are in the cycle.
> 
> Hi Will,
> 
> I didn't see this notice before sending the pull request of vt-d
> patches.

No problem! I was going to drop you a mail asking about that.

> https://lore.kernel.org/linux-iommu/20250714045028.958850-1-baolu.lu@linux.intel.com/
> 
> I cc'ed it to the iommu mailing list. If it happens not appear in your
> mailbox, please let me know, I will send a v2.

I'll grab it today, cheers.

Will

      reply	other threads:[~2025-07-14 10:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-11 14:39 Off for two weeks Jörg Rödel
2025-07-11 16:14 ` Will Deacon
2025-07-14  5:12   ` Baolu Lu
2025-07-14 10:00     ` Will Deacon [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=aHTVT4SEEyZmDdIO@willie-the-truck \
    --to=will@kernel.org \
    --cc=baolu.lu@linux.intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@nvidia.com \
    --cc=joro@8bytes.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox