From: Alex Williamson <alex.williamson@redhat.com>
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: <linux-kernel@vger.kernel.org>, <kvm@vger.kernel.org>,
<diana.craciun@oss.nxp.com>
Subject: Re: [PATCH -next] vfio/fsl-mc: use module_fsl_mc_driver() macro
Date: Fri, 11 Aug 2023 09:18:14 -0600 [thread overview]
Message-ID: <20230811091814.1808a01a.alex.williamson@redhat.com> (raw)
In-Reply-To: <20230811092911.894659-1-yangyingliang@huawei.com>
On Fri, 11 Aug 2023 17:29:11 +0800
Yang Yingliang <yangyingliang@huawei.com> wrote:
> The driver init/exit() function don't do anything special, it
> can use the module_fsl_mc_driver() macro to eliminate boilerplate
> code.
>
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
> ---
> drivers/vfio/fsl-mc/vfio_fsl_mc.c | 14 +-------------
> 1 file changed, 1 insertion(+), 13 deletions(-)
Your colleague submitted a nearly identical patch, but also removing
the redundant module owner, 2 days ago:
https://lore.kernel.org/all/20230809131536.4021639-1-lizetao1@huawei.com/
Thanks,
Alex
>
> diff --git a/drivers/vfio/fsl-mc/vfio_fsl_mc.c b/drivers/vfio/fsl-mc/vfio_fsl_mc.c
> index f2140e94d41e..8053f13c2be5 100644
> --- a/drivers/vfio/fsl-mc/vfio_fsl_mc.c
> +++ b/drivers/vfio/fsl-mc/vfio_fsl_mc.c
> @@ -604,19 +604,7 @@ static struct fsl_mc_driver vfio_fsl_mc_driver = {
> },
> .driver_managed_dma = true,
> };
> -
> -static int __init vfio_fsl_mc_driver_init(void)
> -{
> - return fsl_mc_driver_register(&vfio_fsl_mc_driver);
> -}
> -
> -static void __exit vfio_fsl_mc_driver_exit(void)
> -{
> - fsl_mc_driver_unregister(&vfio_fsl_mc_driver);
> -}
> -
> -module_init(vfio_fsl_mc_driver_init);
> -module_exit(vfio_fsl_mc_driver_exit);
> +module_fsl_mc_driver(vfio_fsl_mc_driver);
>
> MODULE_LICENSE("Dual BSD/GPL");
> MODULE_DESCRIPTION("VFIO for FSL-MC devices - User Level meta-driver");
prev parent reply other threads:[~2023-08-11 15:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 9:29 Yang Yingliang
2023-08-11 15:18 ` Alex Williamson [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=20230811091814.1808a01a.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=diana.craciun@oss.nxp.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yangyingliang@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
all inboxes | Powered by JetHome®