From: Lee Jones <lee.jones@linaro.org>
To: Athira Lekshmi <andnlnbn18@gmail.com>
Cc: rogerable@realtek.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Drivers: memstick: host: Fixed missing a blank line warning
Date: Mon, 8 Dec 2014 08:14:39 +0000 [thread overview]
Message-ID: <20141208081439.GA3951@x1> (raw)
In-Reply-To: <1417943669-4057-1-git-send-email-andnlnbn18@gmail.com>
Not a bad attempt.
The subject line should match the subsystem. You can see what that is
by issuing `git log --oneline -- drivers/memstick/` (supplement
drivers/memstick for the subsystem that you're submitting to).
> Added a new line after declaration to fix the warning message
> 'Missing a blank line after declarations'
>
> Signed-off-by: Athira Lekshmi <andnlnbn18@gmail.com>
> ---
> drivers/memstick/host/rtsx_usb_ms.c | 1 +
> 1 file changed, 1 insertion(+)
Apart from my comment at the top (which a kind maintainer can fix for
you on this occasion I'm sure ;) ), the patch looks good:
Acked-by: Lee Jones <lee.jones@linaro.org>
Now make 3 such changes (you can use checkpatch on some other files)
and send them as a patch-set.
> diff --git a/drivers/memstick/host/rtsx_usb_ms.c b/drivers/memstick/host/rtsx_usb_ms.c
> index a7282b7..cefd745 100644
> --- a/drivers/memstick/host/rtsx_usb_ms.c
> +++ b/drivers/memstick/host/rtsx_usb_ms.c
> @@ -59,6 +59,7 @@ static inline struct device *ms_dev(struct rtsx_usb_ms *host)
> static inline void ms_clear_error(struct rtsx_usb_ms *host)
> {
> struct rtsx_ucr *ucr = host->ucr;
> +
> rtsx_usb_ep0_write_register(ucr, CARD_STOP,
> MS_STOP | MS_CLR_ERR,
> MS_STOP | MS_CLR_ERR);
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2014-12-08 8:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-07 9:14 [PATCH v2] Drivers: memstick: host: Fixed missing a blank line warning Athira Lekshmi
2014-12-08 8:14 ` Lee Jones [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=20141208081439.GA3951@x1 \
--to=lee.jones@linaro.org \
--cc=andnlnbn18@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rogerable@realtek.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