✗ CI.checkpatch: warning for nvme-pci: don't use dma_alloc_noncontiguous with 0 merge boundary

[Patchwork]

== Series Details ==

Series: nvme-pci: don't use dma_alloc_noncontiguous with 0 merge boundary
URL   : https://patchwork.freedesktop.org/series/142082/
State : warning

== Summary ==

+ KERNEL=/kernel
+ git clone https://gitlab.freedesktop.org/drm/maintainer-tools mt
Cloning into 'mt'...
warning: redirecting to https://gitlab.freedesktop.org/drm/maintainer-tools.git/
+ git -C mt rev-list -n1 origin/master
30ab6715fc09baee6cc14cb3c89ad8858688d474
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit be4026493a2e47a106eb5f66d5400b0664f251cc
Author: Christoph Hellwig <hch at lst.de>
Date:   Wed Dec 4 11:36:01 2024 +0530

    nvme-pci: don't use dma_alloc_noncontiguous with 0 merge boundary
    
    Only call into nvme_alloc_host_mem_single which uses
    dma_alloc_noncontiguous when there is non-null dma merge boundary.
    Without this we'll call into dma_alloc_noncontiguous for device using
    dma-direct, which can work fine as long as the preferred size is below the
    MAX_ORDER of the page allocator, but blows up with a warning if it is
    too large.
    
    Fixes: 63a5c7a4b4c4 ("nvme-pci: use dma_alloc_noncontigous if possible")
    Reported-by: Leon Romanovsky <leon at kernel.org>
    Reported-by: Chaitanya Kumar Borah <chaitanya.kumar.borah at intel.com>
    Signed-off-by: Christoph Hellwig <hch at lst.de>
    References: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13227
    Link: https://lore.kernel.org/linux-nvme/39a67024-2926-4a20-8feb-77dd64ab7c39@kernel.dk/T/#mfef47937b20e33aa3cc63a3af930f8a9f9baf8c2
+ /mt/dim checkpatch 40be916657d26be563dbbd2b618cc398ea9aeb33 drm-intel
be4026493a2e nvme-pci: don't use dma_alloc_noncontiguous with 0 merge boundary
-:15: WARNING:BAD_REPORTED_BY_LINK: Reported-by: should be immediately followed by Closes: with a URL to the report
#15: 
Reported-by: Leon Romanovsky <leon at kernel.org>
Reported-by: Chaitanya Kumar Borah <chaitanya.kumar.borah at intel.com>

-:16: WARNING:BAD_REPORTED_BY_LINK: Reported-by: should be immediately followed by Closes: with a URL to the report
#16: 
Reported-by: Chaitanya Kumar Borah <chaitanya.kumar.borah at intel.com>
Signed-off-by: Christoph Hellwig <hch at lst.de>

total: 0 errors, 2 warnings, 0 checks, 15 lines checked