[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <76e7b9fe-5ee5-83f6-0e91-4d07e8e821f8@linux.intel.com>
Date: Sat, 14 Jan 2023 14:44:04 +0800
From: Baolu Lu <baolu.lu@...ux.intel.com>
To: Jason Gunthorpe <jgg@...pe.ca>, Joerg Roedel <joro@...tes.org>
Cc: baolu.lu@...ux.intel.com, Will Deacon <will@...nel.org>,
Robin Murphy <robin.murphy@....com>,
Vasant Hegde <vasant.hegde@....com>,
Chunyan Zhang <zhang.lyra@...il.com>,
Sven Peter <sven@...npeter.dev>, iommu@...ts.linux.dev,
linux-kernel@...r.kernel.org, Joerg Roedel <jroedel@...e.de>
Subject: Re: [PATCH] iommu/ipmmu-vmsa: Remove ipmmu_utlb_disable()
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
Powered by blists - more mailing lists