From: Will Deacon <will@kernel.org>
To: Joerg Roedel <joro@8bytes.org>
Cc: iommu@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, robin.murphy@arm.com,
kernel-team@android.com
Subject: Re: [GIT PULL] iommu/arm-smmu: Updates for 6.10
Date: Tue, 7 May 2024 10:35:17 +0100 [thread overview]
Message-ID: <20240507093517.GA22060@willie-the-truck> (raw)
In-Reply-To: <ZjTk0YG4aJZiF0d2@8bytes.org>
On Fri, May 03, 2024 at 03:21:21PM +0200, Joerg Roedel wrote:
> On Fri, May 03, 2024 at 12:10:37PM +0100, Will Deacon wrote:
> > git://git.kernel.org/pub/scm/linux/kernel/git/will/linux.git tags/arm-smmu-updates
>
> Pulled, thanks Will.
>
> Pushing might take some time, as I temprarily lost access to my
> compile-test machine.
I can see 'em in linux-next now, so looks like it worked out.
Thanks!
Will
prev parent reply other threads:[~2024-05-07 9:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 11:10 [GIT PULL] iommu/arm-smmu: Updates for 6.10 Will Deacon
2024-05-03 13:21 ` Joerg Roedel
2024-05-07 9:35 ` 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=20240507093517.GA22060@willie-the-truck \
--to=will@kernel.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).