...@google.com; a...@arndb.de;
m...@redhat.com
Subject: Re: [PATCH v3] PCI: Add pci_iounmap
On 2020/8/25 9:25, kernel test robot wrote:
Hi George,
I love your patch! Yet something to improve:
[auto build test ERROR on pci/next]
[also build test ERROR on linux/master linus/master asm-generic/master
v5.9
a...@arndb.de;
> m...@redhat.com
> Subject: Re: [PATCH v3] PCI: Add pci_iounmap
>
>
>
>
> On 2020/8/25 9:25, kernel test robot wrote:
> > Hi George,
> >
> > I love your patch! Yet something to improve:
> >
> > [auto build test ERROR on pci/next]
>
On 2020/8/25 9:25, kernel test robot wrote:
Hi George,
I love your patch! Yet something to improve:
[auto build test ERROR on pci/next]
[also build test ERROR on linux/master linus/master asm-generic/master v5.9-rc2
next-20200824]
[If your patch is applied to the wrong git tree, kindly drop
Hi George,
I love your patch! Yet something to improve:
[auto build test ERROR on pci/next]
[also build test ERROR on linux/master linus/master asm-generic/master v5.9-rc2
next-20200824]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest
In case if any architecture selects CONFIG_GENERIC_PCI_IOMAP and not
CONFIG_GENERIC_IOMAP, then the pci_iounmap function is reduced to a NULL
function. Due to this the managed release variants or even the explicit
pci_iounmap calls doesn't really remove the mappings.
This issue is seen on an arm64
5 matches
Mail list logo