Re: [PATCH 6.1.y v2 3/4] mm: refactor arch_calc_vm_flag_bits() and arm64 MTE handling

[Sasha Levin <sashal@kernel.org>]

On Tue, Nov 19, 2024 at 12:40:03PM +0530, Harshit Mogalapalli wrote:
>Hi Sasha,
>
>On 19/11/24 10:06, Sasha Levin wrote:
>>[ Sasha's backport helper bot ]
>>
>>Hi,
>>
>>The upstream commit SHA1 provided is correct: 5baf8b037debf4ec60108ccfeccb8636d1dbad81
>>
>
>Nice bot!
>
>Just few thoughts:
>
>>Commit in newer trees:
>>
>>|-----------------|----------------------------------------------|
>>| 6.11.y          |  Present (different SHA1: 9f5efc1137ba)      |
>>| 6.6.y           |  Not found                                   |
>>| 6.1.y           |  Not found                                   |
>>|-----------------|----------------------------------------------|
>>
>
>
>Given that this patch is for 6.1.y, it(6.1.y) need not be considered 
>as newer tree I think ?

I've kept it in just because sometimes we might do the backport
ourselves and then someone else will send another backport. I agree that
this could be clearer :)

>Also the backport for 6.6.y is present on lore.stable [1], so the 
>backport not being present in stable-6.6.y might be not very useful, 
>as it is possible for people to send the backport to multiple trees in 
>the same stable update cycle(before 6.6.y has the backport included) 
>-- instead could we run this while queuing up(maybe warn if it is 
>neither present in stable-queue-6.6 nor in stable-6.6.y ?) ?

Yeah... Automation is a work in progress. Ideally one day this will turn
into the backend of a dashboard that'll keep track of outstanding
backports.

-- 
Thanks,
Sasha