From: Bjorn Helgaas <helgaas@kernel.org>
To: Liu Shixin <liushixin2@huawei.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Alexander Duyck <alexander.h.duyck@intel.com>
Subject: Re: [PATCH -next] PCI/IOV: use module_pci_driver to simplify the code
Date: Thu, 17 Sep 2020 11:51:43 -0500 [thread overview]
Message-ID: <20200917165143.GA1707439@bjorn-Precision-5520> (raw)
In-Reply-To: <20200917071042.1909191-1-liushixin2@huawei.com>
[+cc Alexander]
On Thu, Sep 17, 2020 at 03:10:42PM +0800, Liu Shixin wrote:
> Use the module_pci_driver() macro to make the code simpler
> by eliminating module_init and module_exit calls.
>
> Signed-off-by: Liu Shixin <liushixin2@huawei.com>
Applied to pci/misc for v5.10, thanks!
> ---
> drivers/pci/pci-pf-stub.c | 14 +-------------
> 1 file changed, 1 insertion(+), 13 deletions(-)
>
> diff --git a/drivers/pci/pci-pf-stub.c b/drivers/pci/pci-pf-stub.c
> index a0b2bd6c918a..45855a5e9fca 100644
> --- a/drivers/pci/pci-pf-stub.c
> +++ b/drivers/pci/pci-pf-stub.c
> @@ -37,18 +37,6 @@ static struct pci_driver pf_stub_driver = {
> .probe = pci_pf_stub_probe,
> .sriov_configure = pci_sriov_configure_simple,
> };
> -
> -static int __init pci_pf_stub_init(void)
> -{
> - return pci_register_driver(&pf_stub_driver);
> -}
> -
> -static void __exit pci_pf_stub_exit(void)
> -{
> - pci_unregister_driver(&pf_stub_driver);
> -}
> -
> -module_init(pci_pf_stub_init);
> -module_exit(pci_pf_stub_exit);
> +module_pci_driver(pf_stub_driver);
>
> MODULE_LICENSE("GPL");
> --
> 2.25.1
>
next prev parent reply other threads:[~2020-09-17 17:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 7:10 [PATCH -next] PCI/IOV: use module_pci_driver to simplify the code Liu Shixin
2020-09-17 16:51 ` Bjorn Helgaas [this message]
2020-09-17 17:19 ` Alexander Duyck
2020-09-17 17:42 ` Bjorn Helgaas
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=20200917165143.GA1707439@bjorn-Precision-5520 \
--to=helgaas@kernel.org \
--cc=alexander.h.duyck@intel.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=liushixin2@huawei.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;
as well as URLs for NNTP newsgroup(s).