Hello, [...] > > > Changes from v3: > > > https://lore.kernel.org/linux-pci/20231215022955.3574063-1-yoshihiro.shimoda.uh@xxxxxxxxxxx/ > > > - Based on the latest pci.git / next branch. So, I modified the patch 1/6 > > > for pci-layerscape.c. Shimoda-san, don't use next when working on patches. I might have told you this once before, per the following. Something that is easy to forget. https://lore.kernel.org/all/20230828160712.GA2127814@rocinante/ This is the HEAD branch you should be using: https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git/log/ You should seldom use our "next" or the upstream "linux-next" when working on a series you want to send to us. That is, unless someone explicitly asks you to do so or the changes you wish to submit to be applied are simple. > > > - Add Reviewed-by tag in the patch 4/6. > > > - Fix locations of read/write accessors by grouped for readability in > > > the patch 4/6. > > > > The series has got all the Mani's acks. The last nitpick was fixed in > > v4. No more comments at least from my side. What about merging it in > > (before merge window v6.8 is opened)? > > Serge, thank you for your comment. > > Hi Krzysztof, Lorenzo, Bjorn, Mani, Hi. Happy New Year 2024! > Would you apply this patch series into pci.git / next branch? We don't apply specific series like that. Bjorn will collect other branches, and then eventually update our "next", which then will be picked up and the upstream "linux-next" will eventually include it. > I confirmed that the patch series could be applied on the latest pci.git / next branch [...] I appreciate that. However, I now need to resolve some conflicts to apply this series. See my comment above. :) Krzysztof
