Comment 7 for bug 1855303

Revision history for this message
Vignesh Gunasekaran (vignesh-g) wrote :

>So I appreciate the patch set you've provided, but due to the number of patches, what I need to do is >cherry-pick them from mainline and push a branch with cherry picks rather than 70+ patches that need to be >reviewed/applied by the kernel team.
>
>And because I can't find these in mainline at all (I've just checked all the proposed commit ids against the >most recent updates to mainline) I can't cherry pick these. Do you know when they'll be accepted upstream?
>
>I also checked against Linus tree and cant find those commit IDs there either.

Jeff,

All of those 72 patches are already accepted by the Kernel community and most of them are already pulled into linus.git except for the ones you listed. But, the ones you have listed are present in mkp/scsi.git.

Even when I was creating a patchset I went by searching those commit IDs, but couldn't find them either in linus.git or mkp/scsi.git. I guess those commit IDs were from local git. So, I found the equivalent commit IDs for those patches in mkp/scsi.git and cherry-picked them.

Ultimately, all 72 patches are already cherry-picked from either linus.git or mkp/scsi.git. The patchset has the cherry-pick reference in it.

I verified the patchset applies cleanly on the focal tree using:

#git am /<patches_directory>/*.patch

I thought executing this command is all you have to do it from your end.

Regarding comment 6:

>Additionally, this one does not cleanly apply when cherry-picked:
>765ab6cdac3b681952da0e22184bf6cf1ae41cf8 scsi: lpfc: Fix a kernel
>warning triggered by lpfc_get_sgl_per_hdwq()

This commit is already pulled into the focal tree from upstream.