From: Ian Abbott <abbotti@mev.co.uk>
To: Raghavendra Ganiga <ravi23ganiga@gmail.com>,
<hsweeten@visionengravers.com>, <gregkh@linuxfoundation.org>
Cc: <devel@driverdev.osuosl.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: comedi: fix coding style issues in comedi_fops.c
Date: Thu, 1 May 2014 10:05:20 +0100 [thread overview]
Message-ID: <53620E50.8000406@mev.co.uk> (raw)
In-Reply-To: <1398932592-17768-1-git-send-email-ravi23ganiga@gmail.com>
On 2014/05/01 09:23 AM, Raghavendra Ganiga wrote:
> This is a patch to fix coding style
> warnings found by checkpatch.pl tool
>
> Signed-off-by: Raghavendra Chandra Ganiga <ravi23ganiga@gmail.com>
> ---
> drivers/staging/comedi/comedi_fops.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/staging/comedi/comedi_fops.c b/drivers/staging/comedi/comedi_fops.c
> index 70545e6..b24bf9b 100644
> --- a/drivers/staging/comedi/comedi_fops.c
> +++ b/drivers/staging/comedi/comedi_fops.c
> @@ -668,6 +668,7 @@ static int do_devconfig_ioctl(struct comedi_device *dev,
> return -EBUSY;
> if (dev->attached) {
> struct module *driver_module = dev->driver->module;
> +
> comedi_device_detach(dev);
> module_put(driver_module);
> }
> @@ -2653,6 +2654,7 @@ static int __init comedi_init(void)
> /* create devices files for legacy/manual use */
> for (i = 0; i < comedi_num_legacy_minors; i++) {
> struct comedi_device *dev;
> +
> dev = comedi_alloc_board_minor(NULL);
> if (IS_ERR(dev)) {
> comedi_cleanup_board_minors();
>
Reviewed-by: Ian Abbott <abbotti@mev.co.uk>
--
-=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=-
-=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=-
next prev parent reply other threads:[~2014-05-01 9:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-01 8:23 [PATCH] staging: comedi: fix coding style issues in comedi_fops.c Raghavendra Ganiga
2014-05-01 9:05 ` Ian Abbott [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-04-30 17:34 Raghavendra Ganiga
2014-04-30 19:59 ` Dan Carpenter
2014-05-01 9:01 ` Ian Abbott
2014-04-25 17:50 RAGHAVENDRA GANIGA
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=53620E50.8000406@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hsweeten@visionengravers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ravi23ganiga@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.