From: Rodolfo Giometti <giometti@enneenne.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-kernel@vger.kernel.org
Cc: gregkh@linuxfoundation.org
Subject: Re: [PATCH v1 1/1] pps: clients: parport: Switch to use module_parport_driver()
Date: Tue, 11 May 2021 09:05:00 +0200 [thread overview]
Message-ID: <77c821e1-adc7-4088-0dcb-da65ba7a39a2@enneenne.com> (raw)
In-Reply-To: <20210510141302.56654-1-andriy.shevchenko@linux.intel.com>
On 10/05/21 16:13, Andy Shevchenko wrote:
> Switch to use module_parport_driver() to reduce boilerplate code.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> drivers/pps/clients/pps_parport.c | 42 ++++++-------------------------
> 1 file changed, 8 insertions(+), 34 deletions(-)
>
> diff --git a/drivers/pps/clients/pps_parport.c b/drivers/pps/clients/pps_parport.c
> index 7a41fb7b0dec..42f93d4c6ee3 100644
> --- a/drivers/pps/clients/pps_parport.c
> +++ b/drivers/pps/clients/pps_parport.c
> @@ -22,8 +22,6 @@
> #include <linux/parport.h>
> #include <linux/pps_kernel.h>
>
> -#define DRVDESC "parallel port PPS client"
> -
> /* module parameters */
>
> #define CLEAR_WAIT_MAX 100
> @@ -138,6 +136,12 @@ static void parport_attach(struct parport *port)
> .dev = NULL
> };
>
> + if (clear_wait > CLEAR_WAIT_MAX) {
> + pr_err("clear_wait value should be not greater then %d\n",
> + CLEAR_WAIT_MAX);
> + return;
> + }
> +
Why do you need to do so? Maybe a comment would be welcomed.
> device = kzalloc(sizeof(struct pps_client_pp), GFP_KERNEL);
> if (!device) {
> pr_err("memory allocation failed, not attaching\n");
> @@ -214,38 +218,8 @@ static struct parport_driver pps_parport_driver = {
> .detach = parport_detach,
> .devmodel = true,
> };
> -
> -/* module staff */
> -
> -static int __init pps_parport_init(void)
> -{
> - int ret;
> -
> - pr_info(DRVDESC "\n");
> -
> - if (clear_wait > CLEAR_WAIT_MAX) {
> - pr_err("clear_wait value should be not greater"
> - " then %d\n", CLEAR_WAIT_MAX);
> - return -EINVAL;
> - }
> -
> - ret = parport_register_driver(&pps_parport_driver);
> - if (ret) {
> - pr_err("unable to register with parport\n");
> - return ret;
> - }
> -
> - return 0;
> -}
> -
> -static void __exit pps_parport_exit(void)
> -{
> - parport_unregister_driver(&pps_parport_driver);
> -}
> -
> -module_init(pps_parport_init);
> -module_exit(pps_parport_exit);
> +module_parport_driver(pps_parport_driver);
>
> MODULE_AUTHOR("Alexander Gordeev <lasaine@lvk.cs.msu.su>");
> -MODULE_DESCRIPTION(DRVDESC);
> +MODULE_DESCRIPTION("parallel port PPS client");
> MODULE_LICENSE("GPL");
>
Ciao,
Rodolfo
--
GNU/Linux Solutions e-mail: giometti@enneenne.com
Linux Device Driver giometti@linux.it
Embedded Systems phone: +39 349 2432127
UNIX programming skype: rodolfo.giometti
next prev parent reply other threads:[~2021-05-11 7:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 14:13 Andy Shevchenko
2021-05-11 7:05 ` Rodolfo Giometti [this message]
2021-05-11 7:18 ` Andy Shevchenko
2021-05-11 7:26 ` Rodolfo Giometti
2021-05-11 7:50 ` Andy Shevchenko
2021-05-11 8:46 ` Rodolfo Giometti
2021-05-11 14:11 ` Andy Shevchenko
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=77c821e1-adc7-4088-0dcb-da65ba7a39a2@enneenne.com \
--to=giometti@enneenne.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
/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®