On Mon, Sep 26, 2022 at 09:30:48PM +0800, Zhuo Chen wrote: > On 9/23/22 4:02 AM, Bjorn Helgaas wrote: > > On Mon, Sep 12, 2022 at 01:09:05AM +0800, Zhuo Chen wrote: > > > On 9/12/22 12:22 AM, Serge Semin wrote: > > > > On Fri, Sep 02, 2022 at 02:16:32AM +0800, Zhuo Chen wrote: > > > ‘pci_aer_clear_nonfatal_status()’ in drivers/crypto/hisilicon/qm.c will be > > > removed in the next kernel: > > > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/crypto/hisilicon/qm.c?id=00278564a60e11df8bcca0ececd8b2f55434e406 > > > > This is a problem because 00278564a60e ("crypto: hisilicon - Remove > > pci_aer_clear_nonfatal_status() call") is in Herbert's cryptodev tree, > > and if I apply this series to the PCI tree and Linus merges it before > > Herbert's cryptodev changes, it will break the build. > > > > I think we need to split this patch up like this: > > > > - Add pci_aer_clear_uncorrect_error_status() to PCI core > > - Convert dpc to use pci_aer_clear_uncorrect_error_status() > > (I might end up squashing with above) > > - Convert lpfc to use pci_aer_clear_uncorrect_error_status() > > - Convert ntb_hw_idt to use pci_aer_clear_uncorrect_error_status() > > - Unexport pci_aer_clear_nonfatal_status() > > > > Then I can apply all but the last patch safely. If the crypto changes > > are merged first, we can add the last one; otherwise we can do it for > > the next cycle. > > > Good proposal. I will implement these in the next version. > > Do I need to put pci related modifications (include patch 2/3 and 3/3) in a > patch set or just single patches? When in doubt, put them in separate patches. It's trivial for me to squash them together if that makes more sense, but much more difficult for me to split them apart. Thanks for helping clean up this area! Bjorn
