From: Greg KH <gregkh@linuxfoundation.org>
To: Benedict Boerger <benedict.boerger@cs.tu-dortmund.de>
Cc: linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: [PATCH] staging: keucr: fix Missing blank line after declarations
Date: Wed, 18 Jun 2014 15:25:37 -0700 [thread overview]
Message-ID: <20140618222537.GA2419@kroah.com> (raw)
In-Reply-To: <1402774793-17224-1-git-send-email-benedict.boerger@cs.tu-dortmund.de>
On Sat, Jun 14, 2014 at 09:39:53PM +0200, Benedict Boerger wrote:
> fix two Missing blank line after declarations issue reported by checkpatch.pl
>
> Done to complete an eudyptula task.
>
> Signed-off-by: Benedict Boerger <benedict.boerger@cs.tu-dortmund.de>
> ---
> drivers/staging/keucr/usb.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/staging/keucr/usb.c b/drivers/staging/keucr/usb.c
> index 12ebde7..dbbd63f 100644
> --- a/drivers/staging/keucr/usb.c
> +++ b/drivers/staging/keucr/usb.c
> @@ -37,6 +37,7 @@ MODULE_DEVICE_TABLE(usb, eucr_usb_ids);
> static int eucr_suspend(struct usb_interface *iface, pm_message_t message)
> {
> struct us_data *us = usb_get_intfdata(iface);
> +
> pr_info("--- eucr_suspend ---\n");
> /* Wait until no command is running */
> mutex_lock(&us->dev_mutex);
> @@ -53,6 +54,7 @@ static int eucr_resume(struct usb_interface *iface)
> u8 tmp = 0;
>
> struct us_data *us = usb_get_intfdata(iface);
> +
> pr_info("--- eucr_resume---\n");
> mutex_lock(&us->dev_mutex);
>
Sorry, someone beat you to this file by 2 days, and the fix is now in my
tree :(
greg k-h
prev parent reply other threads:[~2014-06-18 22:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-14 19:39 [PATCH] staging: keucr: fix Missing blank line after declarations Benedict Boerger
2014-06-18 22:25 ` Greg KH [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=20140618222537.GA2419@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=benedict.boerger@cs.tu-dortmund.de \
--cc=devel@driverdev.osuosl.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