Message ID | cover.1641500561.git.christophe.jaillet@wanadoo.fr |
---|---|
Headers | show |
Series | Remove usage of the deprecated "pci-dma-compat.h" API | expand |
On Thu, 6 Jan 2022 22:45:13 +0100, Christophe JAILLET wrote: > This serie axes all the remaining usages of the deprecated "pci-dma-compat.h" > API. > > All these patches have already been posted. > > They have been generated with a coccinelle script. > The tricky parts are patches that use dma_alloc_coherent() because the correct > GFP flag has to be used in place of the previous embedded GFP_ATOMIC. > > [...] Applied to 5.17/scsi-queue, thanks! [10/16] scsi: message: fusion: Remove usage of the deprecated "pci-dma-compat.h" API https://git.kernel.org/mkp/scsi/c/b114dda6f2f1 [11/16] scsi: mptbase: Use dma_alloc_coherent() in 'mpt_alloc_fw_memory()' https://git.kernel.org/mkp/scsi/c/2d50607260a6 [12/16] scsi: mptbase: Use dma_alloc_coherent() https://git.kernel.org/mkp/scsi/c/5c5e6b6f61e0 [13/16] scsi: mptsas: Use dma_alloc_coherent() in mptsas_exp_repmanufacture_info() https://git.kernel.org/mkp/scsi/c/7a960b3a5e37 [14/16] scsi: mptsas: Use dma_alloc_coherent() https://git.kernel.org/mkp/scsi/c/76a334d756c5 [15/16] scsi: mptctl: Use dma_alloc_coherent() https://git.kernel.org/mkp/scsi/c/706dc3b91989
Hi Christophe, do you know what the state is in current linux-next? I think we'll just want to queue up anything left at this point in the dma-mapping or PCI tree and get it done.
Le 23/02/2022 à 08:46, Christoph Hellwig a écrit : > Hi Christophe, > > do you know what the state is in current linux-next? > > I think we'll just want to queue up anything left at this point in the > dma-mapping or PCI tree and get it done. > Hi, Patch 01, 04, 05, 06, 08, 09 have not reached -next yet. They all still apply cleanly. 04 has been picked it up for inclusion in the media subsystem for 5.18. The other ones all have 1 or more Reviewed-by:/Acked-by: tags. Patch 16 must be resubmitted to add "#include <linux/dma-mapping.h>" in order not to break builds. All the other patches have landed in -next. CJ
On Wed, Feb 23, 2022 at 9:26 PM Christophe JAILLET <christophe.jaillet@wanadoo.fr> wrote: > > Le 23/02/2022 à 08:46, Christoph Hellwig a écrit : > > Hi Christophe, > > > > do you know what the state is in current linux-next? > > > > I think we'll just want to queue up anything left at this point in the > > dma-mapping or PCI tree and get it done. > > > > Hi, > > Patch 01, 04, 05, 06, 08, 09 have not reached -next yet. > They all still apply cleanly. > > 04 has been picked it up for inclusion in the media subsystem for 5.18. > The other ones all have 1 or more Reviewed-by:/Acked-by: tags. > > Patch 16 must be resubmitted to add "#include <linux/dma-mapping.h>" in > order not to break builds. > > > All the other patches have landed in -next. Ok, these all look trivial. I'd suggest you send the rebase version to Andrew Morton then, so he can pick them all up into linux-mm, on top of the linux-next contents. Arnd
On Wed, Feb 23, 2022 at 09:26:56PM +0100, Christophe JAILLET wrote: > Patch 01, 04, 05, 06, 08, 09 have not reached -next yet. > They all still apply cleanly. > > 04 has been picked it up for inclusion in the media subsystem for 5.18. > The other ones all have 1 or more Reviewed-by:/Acked-by: tags. > > Patch 16 must be resubmitted to add "#include <linux/dma-mapping.h>" in > order not to break builds. So how about this: I'll pick up 1, 5,6,8 and 9 for the dma-mapping tree. After -rc1 when presumably all other patches have reached mainline your resubmit one with the added include and we finish this off? Thanks a lot for all your work already!
Le 24/02/2022 à 08:07, Arnd Bergmann a écrit : > On Thu, Feb 24, 2022 at 7:25 AM Christoph Hellwig <hch@infradead.org> wrote: >> On Wed, Feb 23, 2022 at 09:26:56PM +0100, Christophe JAILLET wrote: >>> Patch 01, 04, 05, 06, 08, 09 have not reached -next yet. >>> They all still apply cleanly. >>> >>> 04 has been picked it up for inclusion in the media subsystem for 5.18. >>> The other ones all have 1 or more Reviewed-by:/Acked-by: tags. >>> >>> Patch 16 must be resubmitted to add "#include <linux/dma-mapping.h>" in >>> order not to break builds. >> So how about this: I'll pick up 1, 5,6,8 and 9 for the dma-mapping >> tree. After -rc1 when presumably all other patches have reached >> mainline your resubmit one with the added include and we finish this >> off? > Sounds good to me as well. > > Arnd This is fine for me. When all patches have reached -next, I'll re-submit the fixed 16th patch. Thanks for your assistance for ending this long story :) CJ
I've applied patches 1,5,6,8 and 9 to the dma-mapping tree.