From: Joerg Roedel <joro@8bytes.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org, iommu@lists.linux.dev
Subject: Re: [git pull] IOMMU Updates for Linux v6.3
Date: Fri, 24 Feb 2023 23:09:40 +0100 [thread overview]
Message-ID: <Y/k1pGjjRIznCIu2@8bytes.org> (raw)
In-Reply-To: <CAHk-=wg71g9S0F8V-=97XQsaf6Edbxhfx-xS+x894w8sMZW+=w@mail.gmail.com>
On Fri, Feb 24, 2023 at 01:46:47PM -0800, Linus Torvalds wrote:
> Ok. I wil be doing x86-64 and arm64 allmodconfig builds, but if there
> are any cases outside of that set that triggers, I won't norice.
>
> That _should_ certainly cover the majority of any new code that might
> have a semantic conflict, though.
Aside from the conflicts with upstream, which I resolved in the merge
commit, the only other conflict that Stephen reported for linux-next was
in the rdma tree, iirc. So fingers crossed that this is the only one.
Regards,
Joerg
next prev parent reply other threads:[~2023-02-24 22:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 8:51 [git pull] IOMMU Updates for Linux v6.3 Joerg Roedel
2023-02-24 21:46 ` Linus Torvalds
2023-02-24 22:09 ` Joerg Roedel [this message]
2023-02-24 23:14 ` Linus Torvalds
2023-02-25 6:36 ` Joerg Roedel
2023-02-24 23:27 ` pr-tracker-bot
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=Y/k1pGjjRIznCIu2@8bytes.org \
--to=joro@8bytes.org \
--cc=iommu@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--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