From: Sui Jingfeng <suijingfeng@loongson.cn>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
loongson-kernel@lists.loongnix.cn,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] linux/pci.h: add a dummy implement for pci_clear_master()
Date: Wed, 31 May 2023 17:49:15 +0800 [thread overview]
Message-ID: <835b253a-b8fc-98de-0f5a-7f3ff0010d6c@loongson.cn> (raw)
In-Reply-To: <CAMuHMdVU1qurBki6uf3UadK0Dted67pnhE7+2CDGYmK7QCNY0g@mail.gmail.com>
Hi,
thanks a lot.
On 2023/5/31 15:04, Geert Uytterhoeven wrote:
> Hi Sui,
>
> On Tue, May 30, 2023 at 12:21 PM Sui Jingfeng <suijingfeng@loongson.cn> wrote:
>> As some arch(m68k for example) doesn't have config_pci enabled, drivers[1]
>> call pci_clear_master() without config_pci guard can not built.
>>
>> drivers/gpu/drm/etnaviv/etnaviv_pci_drv.c:
>> In function 'etnaviv_gpu_pci_fini':
>>>> drivers/gpu/drm/etnaviv/etnaviv_pci_drv.c:32:9:
>> error: implicit declaration of function 'pci_clear_master';
>> did you mean 'pci_set_master'? [-Werror=implicit-function-declaration]
>> 32 | pci_clear_master(pdev);
>> | ^~~~~~~~~~~~~~~~
>> | pci_set_master
>> cc1: some warnings being treated as errors
>>
>> [1] https://patchwork.freedesktop.org/patch/539977/?series=118522&rev=1
>>
>> Reported-by: kernel test robot <lkp@intel.com>
>> Closes: https://lore.kernel.org/oe-kbuild-all/202305301659.4guSLavL-lkp@intel.com/
>> Signed-off-by: Sui Jingfeng <suijingfeng@loongson.cn>
> Thanks for your patch!
>
>> --- a/include/linux/pci.h
>> +++ b/include/linux/pci.h
>> @@ -1904,6 +1904,7 @@ static inline int pci_dev_present(const struct pci_device_id *ids)
>> #define pci_dev_put(dev) do { } while (0)
>>
>> static inline void pci_set_master(struct pci_dev *dev) { }
>> +static inline void pci_clear_master(struct pci_dev *dev) { }
>> static inline int pci_enable_device(struct pci_dev *dev) { return -EIO; }
>> static inline void pci_disable_device(struct pci_dev *dev) { }
>> static inline int pcim_enable_device(struct pci_dev *pdev) { return -EIO; }
> Makes perfect sense, given there has been a dummy for pci_set_master()
> since the git stone age. Apparently adding the dummy was forgotten
> when pci_clear_master() was introduced.
>
> Fixes: 6a479079c07211bf ("PCI: Add pci_clear_master() as opposite of
> pci_set_master()")
> Reviewed-by: Geert Uytterhoeven <geert@linux-m68k.org>
>
> Gr{oetje,eeting}s,
>
> Geert
>
--
Jingfeng
next prev parent reply other threads:[~2023-05-31 9:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 10:16 Sui Jingfeng
2023-05-30 20:11 ` Bjorn Helgaas
2023-05-31 4:25 ` Sui Jingfeng
2023-05-31 17:16 ` Bjorn Helgaas
2023-05-31 17:37 ` Sui Jingfeng
2023-05-31 7:04 ` Geert Uytterhoeven
2023-05-31 9:49 ` Sui Jingfeng [this message]
2023-06-06 16:13 ` Bjorn Helgaas
2023-06-06 17:48 ` Sui Jingfeng
2023-06-06 18:46 ` Bjorn Helgaas
2023-06-06 19:13 ` Sui Jingfeng
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=835b253a-b8fc-98de-0f5a-7f3ff0010d6c@loongson.cn \
--to=suijingfeng@loongson.cn \
--cc=bhelgaas@google.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lkp@intel.com \
--cc=loongson-kernel@lists.loongnix.cn \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®