Hi Sasha,
On 25 Mar 2025, at 7:33, Sasha Levin wrote:
[ Sasha's backport helper bot ]
Hi,
Summary of potential issues: ⚠️ Found matching upstream commit but patch is missing proper reference to it
What is the proper way of referring to the original upstream commit? I see “(cherry picked from commit 60cf233b585cdf1f3c5e52d1225606b86acd08b0)” was added in the git log.
I was following the command in[1] to resubmit after I resolved the conflicts.
Thanks.
[1] https://lore.kernel.org/all/2025032403-craziness-tactics-91af@gregkh/
Found matching upstream commit: 60cf233b585cdf1f3c5e52d1225606b86acd08b0
Status in newer kernel trees: 6.13.y | Not found 6.12.y | Not found 6.6.y | Not found
Note: The patch differs from the upstream commit:
1: 60cf233b585cd < -: ------------- mm/migrate: fix shmem xarray update during migration
-: ------------- > 1: 05f98b99ab8a9 mm/migrate: fix shmem xarray update during migration
Results of testing on various branches:
| Branch | Patch Apply | Build Test | |---------------------------|-------------|------------| | stable/linux-6.1.y | Success | Success |
Best Regards, Yan, Zi