From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Qiheng Lin <linqiheng@huawei.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
zhenwei pi <pizhenwei@bytedance.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Mihai Carabas <mihai.carabas@oracle.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Shile Zhang <shile.zhang@linux.alibaba.com>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
Hulk Robot <hulkci@huawei.com>
Subject: Re: [PATCH -next] misc/pvpanic: add missing MODULE_DEVICE_TABLE
Date: Fri, 14 May 2021 09:08:07 +0200 [thread overview]
Message-ID: <YJ4h16jjImjvqAKx@kroah.com> (raw)
In-Reply-To: <20210514070103.540-1-linqiheng@huawei.com>
On Fri, May 14, 2021 at 03:01:03PM +0800, Qiheng Lin wrote:
> This patch adds missing MODULE_DEVICE_TABLE definition which generates
> correct modalias for automatic loading of this driver when it is built
> as an external module.
>
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: Qiheng Lin <linqiheng@huawei.com>
> ---
> drivers/misc/pvpanic/pvpanic-pci.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/misc/pvpanic/pvpanic-pci.c b/drivers/misc/pvpanic/pvpanic-pci.c
> index 9ecc4e8559d5..ccd7e32d3f55 100644
> --- a/drivers/misc/pvpanic/pvpanic-pci.c
> +++ b/drivers/misc/pvpanic/pvpanic-pci.c
> @@ -26,6 +26,7 @@ static const struct pci_device_id pvpanic_pci_id_tbl[] = {
> { PCI_DEVICE(PCI_VENDOR_ID_REDHAT, PCI_DEVICE_ID_REDHAT_PVPANIC)},
> {}
> };
> +MODULE_DEVICE_TABLE(pci, pvpanic_pci_id_tbl);
>
> static ssize_t capability_show(struct device *dev,
> struct device_attribute *attr, char *buf)
>
As I have said before, unless you have a user that reports a real
problem with these types of modules not automatically loading, I am not
going to take these patches, and you should probably stop generating
them.
thanks,
greg k-h
prev parent reply other threads:[~2021-05-14 7:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 7:01 [PATCH -next] misc/pvpanic: add missing MODULE_DEVICE_TABLE Qiheng Lin
2021-05-14 7:08 ` Greg Kroah-Hartman [this message]
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=YJ4h16jjImjvqAKx@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=hulkci@huawei.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linqiheng@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mihai.carabas@oracle.com \
--cc=pbonzini@redhat.com \
--cc=pizhenwei@bytedance.com \
--cc=shile.zhang@linux.alibaba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox