From: Christoph Hellwig <hch@infradead.org>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: Christoph Hellwig <hch@infradead.org>,
arnd@arndb.de, akpm@linux-foundation.org,
ink@jurassic.park.msu.ru, mattst88@gmail.com, mpe@ellerman.id.au,
benh@kernel.crashing.org, paulus@samba.org, davem@davemloft.net,
airlied@linux.ie, vkoul@kernel.org, hao.wu@intel.com,
trix@redhat.com, mdf@kernel.org, yilun.xu@intel.com,
awalls@md.metrocast.net, mchehab@kernel.org,
sathya.prakash@broadcom.com, sreekanth.reddy@broadcom.com,
suganath-prabu.subramani@broadcom.com,
mporter@kernel.crashing.org, alex.bou9@gmail.com,
bhelgaas@google.com, linux-alpha@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, sparclinux@vger.kernel.org,
dmaengine@vger.kernel.org, linux-fpga@vger.kernel.org,
linux-media@vger.kernel.org, MPT-FusionLinux.pdl@broadcom.com,
linux-scsi@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH 00/16] Remove usage of the deprecated "pci-dma-compat.h" API
Date: Wed, 23 Feb 2022 22:25:16 -0800 [thread overview]
Message-ID: <YhckzJp5/x9zW4uQ@infradead.org> (raw)
In-Reply-To: <ddf6010e-417d-8da7-8e11-1b4a55f92fff@wanadoo.fr>
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!
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: airlied@linux.ie, trix@redhat.com, linux-fpga@vger.kernel.org,
linux-pci@vger.kernel.org, paulus@samba.org,
sparclinux@vger.kernel.org, linux-scsi@vger.kernel.org,
sathya.prakash@broadcom.com,
Christoph Hellwig <hch@infradead.org>,
MPT-FusionLinux.pdl@broadcom.com, hao.wu@intel.com,
arnd@arndb.de, suganath-prabu.subramani@broadcom.com,
sreekanth.reddy@broadcom.com, ink@jurassic.park.msu.ru,
bhelgaas@google.com, mchehab@kernel.org, mattst88@gmail.com,
awalls@md.metrocast.net, davem@davemloft.net,
alex.bou9@gmail.com, vkoul@kernel.org,
linux-alpha@vger.kernel.org, dmaengine@vger.kernel.org,
mdf@kernel.org, akpm@linux-foundation.org,
linux-media@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
yilun.xu@intel.com
Subject: Re: [PATCH 00/16] Remove usage of the deprecated "pci-dma-compat.h" API
Date: Wed, 23 Feb 2022 22:25:16 -0800 [thread overview]
Message-ID: <YhckzJp5/x9zW4uQ@infradead.org> (raw)
In-Reply-To: <ddf6010e-417d-8da7-8e11-1b4a55f92fff@wanadoo.fr>
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!
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: Christoph Hellwig <hch@infradead.org>,
arnd@arndb.de, akpm@linux-foundation.org,
ink@jurassic.park.msu.ru, mattst88@gmail.com, mpe@ellerman.id.au,
benh@kernel.crashing.org, paulus@samba.org, davem@davemloft.net,
airlied@linux.ie, vkoul@kernel.org, hao.wu@intel.com,
trix@redhat.com, mdf@kernel.org, yilun.xu@intel.com,
awalls@md.metrocast.net, mchehab@kernel.org,
sathya.prakash@broadcom.com, sreekanth.reddy@broadcom.com,
suganath-prabu.subramani@broadcom.com,
mporter@kernel.crashing.org, alex.bou9@gmail.com,
bhelgaas@google.com, linux-alpha@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, sparclinux@vger.kernel.org,
dmaengine@vger.kernel.org, linux-fpga@vger.kernel.org,
linux-media@vger.kernel.org, MPT-FusionLinux.pdl@broadcom.com,
linux-scsi@vger.kernel.org, linux-pci@vger.ke
Subject: Re: [PATCH 00/16] Remove usage of the deprecated "pci-dma-compat.h" API
Date: Wed, 23 Feb 2022 22:25:16 -0800 [thread overview]
Message-ID: <YhckzJp5/x9zW4uQ@infradead.org> (raw)
In-Reply-To: <ddf6010e-417d-8da7-8e11-1b4a55f92fff@wanadoo.fr>
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!
next prev parent reply other threads:[~2022-02-24 6:26 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 21:45 [PATCH 00/16] Remove usage of the deprecated "pci-dma-compat.h" API Christophe JAILLET
2022-01-06 21:45 ` Christophe JAILLET
2022-01-06 21:46 ` [PATCH 01/16] alpha: " Christophe JAILLET
2022-01-10 8:43 ` Christoph Hellwig
2022-01-06 21:47 ` [PATCH 02/16] floppy: " Christophe JAILLET
2022-01-06 21:47 ` Christophe JAILLET
2022-01-10 8:43 ` Christoph Hellwig
2022-01-10 8:43 ` Christoph Hellwig
2022-01-06 21:49 ` [PATCH 03/16] fpga: dfl: pci: " Christophe JAILLET
2022-01-06 23:06 ` Arnd Bergmann
2022-01-07 0:58 ` Arnd Bergmann
2022-01-07 6:34 ` Christophe JAILLET
2022-01-10 8:44 ` Christoph Hellwig
2022-01-06 21:50 ` [PATCH 04/16] media: " Christophe JAILLET
2022-01-07 0:51 ` Arnd Bergmann
2022-01-07 7:10 ` Mauro Carvalho Chehab
2022-02-18 13:11 ` Hans Verkuil
2022-01-10 8:44 ` Christoph Hellwig
2022-01-06 21:51 ` [PATCH 05/16] agp/intel: " Christophe JAILLET
2022-01-07 0:53 ` Arnd Bergmann
2022-01-10 8:45 ` Christoph Hellwig
2022-01-06 21:51 ` [PATCH 06/16] sparc: " Christophe JAILLET
2022-01-07 0:54 ` Arnd Bergmann
2022-01-07 11:04 ` David Miller
2022-01-10 8:45 ` Christoph Hellwig
2022-01-06 21:52 ` [PATCH 07/16] dmaengine: pch_dma: " Christophe JAILLET
2022-01-07 0:56 ` Arnd Bergmann
2022-01-08 16:47 ` Vinod Koul
2022-01-10 8:45 ` Christoph Hellwig
2022-01-06 21:52 ` [PATCH 08/16] rapidio/tsi721: " Christophe JAILLET
2022-01-07 1:00 ` Arnd Bergmann
2022-01-10 8:46 ` Christoph Hellwig
2022-01-06 21:53 ` [PATCH 09/16] media: v4l2-pci-skeleton: " Christophe JAILLET
2022-01-07 1:01 ` Arnd Bergmann
2022-01-10 8:46 ` Christoph Hellwig
2022-01-06 21:54 ` [PATCH 10/16] scsi: message: fusion: " Christophe JAILLET
2022-01-10 8:47 ` Christoph Hellwig
2022-01-06 21:54 ` [PATCH 11/16] scsi: mptbase: Use dma_alloc_coherent() in 'mpt_alloc_fw_memory()' Christophe JAILLET
2022-01-10 8:47 ` Christoph Hellwig
2022-01-06 21:54 ` [PATCH 12/16] scsi: mptbase: Use dma_alloc_coherent() Christophe JAILLET
2022-01-10 8:47 ` Christoph Hellwig
2022-01-06 21:54 ` [PATCH 13/16] scsi: mptsas: Use dma_alloc_coherent() in mptsas_exp_repmanufacture_info() Christophe JAILLET
2022-01-10 8:48 ` Christoph Hellwig
2022-01-06 21:54 ` [PATCH 14/16] scsi: mptsas: Use dma_alloc_coherent() Christophe JAILLET
2022-01-10 8:48 ` Christoph Hellwig
2022-01-06 21:54 ` [PATCH 15/16] scsi: mptctl: " Christophe JAILLET
2022-01-10 8:48 ` Christoph Hellwig
2022-01-06 21:55 ` [PATCH 16/16] PCI: Remove usage of the deprecated "pci-dma-compat.h" API Christophe JAILLET
2022-01-06 22:28 ` Bjorn Helgaas
2022-01-07 6:34 ` Christophe JAILLET
2022-01-07 17:23 ` Marion & Christophe JAILLET
2022-01-10 8:49 ` Christoph Hellwig
2022-01-07 9:20 ` kernel test robot
2022-01-07 9:41 ` kernel test robot
2022-01-10 15:35 ` [PATCH 00/16] " Martin K. Petersen
2022-01-10 15:35 ` Martin K. Petersen
2022-01-10 15:35 ` Martin K. Petersen
2022-01-19 4:06 ` Martin K. Petersen
2022-01-19 4:06 ` Martin K. Petersen
2022-01-25 19:28 ` Moritz Fischer
2022-01-25 19:28 ` Moritz Fischer
2022-01-25 19:28 ` Moritz Fischer
2022-02-23 7:46 ` Christoph Hellwig
2022-02-23 7:46 ` Christoph Hellwig
2022-02-23 7:46 ` Christoph Hellwig
2022-02-23 20:26 ` Christophe JAILLET
2022-02-23 20:26 ` Christophe JAILLET
2022-02-23 20:42 ` Arnd Bergmann
2022-02-23 20:42 ` Arnd Bergmann
2022-02-23 20:42 ` Arnd Bergmann
2022-02-24 6:25 ` Christoph Hellwig [this message]
2022-02-24 6:25 ` Christoph Hellwig
2022-02-24 6:25 ` Christoph Hellwig
2022-02-24 7:07 ` Arnd Bergmann
2022-02-24 7:07 ` Arnd Bergmann
2022-02-24 7:07 ` Arnd Bergmann
2022-02-24 18:15 ` Christophe JAILLET
2022-02-24 18:15 ` Christophe JAILLET
2022-02-24 18:15 ` Christophe JAILLET
2022-02-25 16:20 ` Christoph Hellwig
2022-02-25 16:20 ` Christoph Hellwig
2022-02-25 16:20 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YhckzJp5/x9zW4uQ@infradead.org \
--to=hch@infradead.org \
--cc=MPT-FusionLinux.pdl@broadcom.com \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=alex.bou9@gmail.com \
--cc=arnd@arndb.de \
--cc=awalls@md.metrocast.net \
--cc=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=davem@davemloft.net \
--cc=dmaengine@vger.kernel.org \
--cc=hao.wu@intel.com \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mattst88@gmail.com \
--cc=mchehab@kernel.org \
--cc=mdf@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=mporter@kernel.crashing.org \
--cc=paulus@samba.org \
--cc=sathya.prakash@broadcom.com \
--cc=sparclinux@vger.kernel.org \
--cc=sreekanth.reddy@broadcom.com \
--cc=suganath-prabu.subramani@broadcom.com \
--cc=trix@redhat.com \
--cc=vkoul@kernel.org \
--cc=yilun.xu@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.