From: Baolu Lu <baolu.lu@linux.intel.com>
To: Jason Gunthorpe <jgg@ziepe.ca>, Joerg Roedel <joro@8bytes.org>
Cc: baolu.lu@linux.intel.com, Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Vasant Hegde <vasant.hegde@amd.com>,
Chunyan Zhang <zhang.lyra@gmail.com>,
Sven Peter <sven@svenpeter.dev>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
Joerg Roedel <jroedel@suse.de>
Subject: Re: [PATCH] iommu/ipmmu-vmsa: Remove ipmmu_utlb_disable()
Date: Sat, 14 Jan 2023 14:44:04 +0800 [thread overview]
Message-ID: <76e7b9fe-5ee5-83f6-0e91-4d07e8e821f8@linux.intel.com> (raw)
In-Reply-To: <Y8G06onFowE3ZIy8@ziepe.ca>
On 2023/1/14 3:45, Jason Gunthorpe wrote:
> On Fri, Jan 13, 2023 at 08:25:17PM +0100, Joerg Roedel wrote:
>> On Fri, Jan 13, 2023 at 03:12:21PM -0400, Jason Gunthorpe wrote:
>>> I'm surprised the 0-day bot didn't notice?
>>
>> Well, I think 0-day does not spend that much time on iommu patch-sets,
>> especially doing randconfigs or allyes/modconfigs.
>
> Intel folks, can you check on this with the 0-day team? Perhaps since
> the list was moved it is not properly subscribed.
I've forwarded this thread to the Intel 0-day team.
>
>> In general it is a good idea to at least compile-test every file that is
>> changed in a patch-set before sending it out and not rely on 0-day bot
>> for that.
>
> Against every arch combination? This is why we have automation bots :(
>
> Jason
>
--
Best regards,
baolu
prev parent reply other threads:[~2023-01-14 6:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 18:56 [PATCH] iommu/ipmmu-vmsa: Remove ipmmu_utlb_disable() Joerg Roedel
2023-01-13 19:12 ` Jason Gunthorpe
2023-01-13 19:25 ` Joerg Roedel
2023-01-13 19:45 ` Jason Gunthorpe
2023-01-13 21:29 ` Joerg Roedel
2023-01-14 6:48 ` Baolu Lu
2023-01-14 6:44 ` Baolu Lu [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=76e7b9fe-5ee5-83f6-0e91-4d07e8e821f8@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=sven@svenpeter.dev \
--cc=vasant.hegde@amd.com \
--cc=will@kernel.org \
--cc=zhang.lyra@gmail.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