From: Paul Bolle <pebolle@tiscali.nl>
To: Peter Hung <hpeter@gmail.com>
Cc: johan@kernel.org, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
tom_tsai@fintek.com.tw, peter_hong@fintek.com.tw,
Peter Hung <hpeter+linux_kernel@gmail.com>
Subject: Re: [PATCH V4 1/1] usb:serial:f81534 add F81532/534 driver
Date: Wed, 15 Jul 2015 10:36:45 +0200 [thread overview]
Message-ID: <1436949405.2679.67.camel@tiscali.nl> (raw)
In-Reply-To: <1436843584-22616-1-git-send-email-hpeter+linux_kernel@gmail.com>
Just a few nits, I'm afraid.
On di, 2015-07-14 at 11:13 +0800, Peter Hung wrote:
> --- /dev/null
> +++ b/drivers/usb/serial/f81534.c
> +int f81534_gpio_request(struct gpio_chip *chip, unsigned offset)
> +{
> + [...]
> +}
static?
> +void f81534_gpio_free(struct gpio_chip *chip, unsigned offset)
> +{
> + [...]
> +}
Ditto.
> +static struct gpio_chip f81534_gpio_chip_templete = {
> + [...]
> + .request = f81534_gpio_request,
> + .free = f81534_gpio_free,
> + [...]
> +};
> +int f81534_ioctl_set_rs485(struct usb_serial_port *port,
> + struct serial_rs485 __user *arg)
> +{
> + [...]
> +}
Ditto.
> +static int f81534_ioctl(struct tty_struct *tty, unsigned int cmd,
> + unsigned long arg)
> +{
> + [...]
> + case TIOCSRS485:
> + return f81534_ioctl_set_rs485(port,
> + (struct serial_rs485 __user *)
> + arg);
> + [...]
> +}
> +int f81534_prepare_write_buffer(struct usb_serial_port *port,
> + void *dest, size_t size)
> +{
> + [...]
> +}
Ditto.
> +static struct usb_serial_driver f81534_device = {
> + [...]
> + .prepare_write_buffer = f81534_prepare_write_buffer,
> + .[...]
> +};
> +
> +static struct usb_serial_driver *const serial_drivers[] = {
> + &f81534_device, NULL
> +};
> +
If you drop this empty line ...
> +module_usb_serial_driver(serial_drivers, id_table);
and add an empty line here, things look neater.
> +MODULE_DESCRIPTION(DRIVER_DESC);
> +MODULE_AUTHOR("Peter Hong <Peter_Hong@fintek.com.tw>");
> +MODULE_AUTHOR("Tom Tsai <Tom_Tsai@fintek.com.tw>");
> +MODULE_LICENSE("GPL");
Thanks,
Paul Bolle
next prev parent reply other threads:[~2015-07-15 8:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 3:13 [PATCH V4 1/1] usb:serial:f81534 add F81532/534 driver Peter Hung
2015-07-15 8:36 ` Paul Bolle [this message]
2015-07-15 8:55 ` Peter Hung
2015-07-15 9:53 ` Johan Hovold
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=1436949405.2679.67.camel@tiscali.nl \
--to=pebolle@tiscali.nl \
--cc=gregkh@linuxfoundation.org \
--cc=hpeter+linux_kernel@gmail.com \
--cc=hpeter@gmail.com \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter_hong@fintek.com.tw \
--cc=tom_tsai@fintek.com.tw \
/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