Context
A Kernel Patch
- The follow patch looks potentially relevant:
https://patchwork.kernel.org/project/linux-rockchip/patch/20250509-b4-pci_dwc_reset_support-v3-1-37e96b4692e7@wdc.com/
git clone https://github.com/torvalds/linux.git (Is there a better place? kernel.org is pretty opaque)
are the pre-reqs in mnt kernel? The patch header contains
base-commit: 08733088b566b58283f0f12fb73f5db6a9a9de30
change-id: 20250430-b4-pci_dwc_reset_support-d720dbafb7ea
prerequisite-change-id: 20250404-pcie-reset-slot-730bfa71a202:v4
prerequisite-patch-id: 2dad85eb26838d89569b12c19d70f392fa592667
prerequisite-patch-id: 6238a682bd8e9476e5911b7a59263c3fc618d63e
prerequisite-patch-id: 37cab00bc255a62b1e8396a48a3afba5e1751abd
prerequisite-patch-id: ff711f65cf9926374646b76cd38bdd823d576764
prerequisite-patch-id: 1654cca919d024b9a9190b28e90f722975c797e8
- First check and see what is upstream. I had to remember how to use
git-patch-idand also how to split a long regex disjunction into multiple lines.
git log --patch --no-merges v6.13.. | \
git patch-id --stable | \
grep -F -e 2dad85eb26838d89569b12c19d70f392fa592667 \
-e 6238a682bd8e9476e5911b7a59263c3fc618d63e \
-e 37cab00bc255a62b1e8396a48a3afba5e1751abd \
-e ff711f65cf9926374646b76cd38bdd823d576764 \
-e 1654cca919d024b9a9190b28e90f722975c797e8
yields
37cab00bc255a62b1e8396a48a3afba5e1751abd d1c696dba120624256ab335ab8247f535b872309
2dad85eb26838d89569b12c19d70f392fa592667 b06d125e6280603a34d9064cd9c12748ca2edb04
The two commits that are actually found, are only in tag 'v6.16~rc1'
- The discussion on LKML mentions
pci/slot-reset. Where does that branch live?
git remote add pci https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git
git fetch pci
git for-each-ref refs/remotes/pci --format "%(refname)" | \
while read branch
do
echo "checking $branch"
git log --patch --no-merges --since 2025-01-01 $branch | \
git patch-id --stable | \
grep -F -e 2dad85eb26838d89569b12c19d70f392fa592667 \
-e 6238a682bd8e9476e5911b7a59263c3fc618d63e \
-e 37cab00bc255a62b1e8396a48a3afba5e1751abd \
-e ff711f65cf9926374646b76cd38bdd823d576764 \
-e 1654cca919d024b9a9190b28e90f722975c797e8
done
This did not find any more commits, but I did learn how to use
git-for-each-ref, so I guess not a total loss.