From: Greg KH <gregkh@linuxfoundation.org>
To: nicolas@autobyte.com.br
Cc: linux@rasmusvillemoes.dk, pure.logic@nexus-software.ie,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
lkcamp@lists.libreplanetbr.org
Subject: Re: [PATCH] staging: mt7621-mmc: Add blank line after declaration
Date: Wed, 7 Nov 2018 12:26:50 +0100 [thread overview]
Message-ID: <20181107112650.GA29485@kroah.com> (raw)
In-Reply-To: <20181107004242.1486-1-nfraprado@protonmail.com>
On Tue, Nov 06, 2018 at 10:42:42PM -0200, nicolas@autobyte.com.br wrote:
> From: Nícolas F. R. A. Prado <nfraprado@protonmail.com>
>
> Correct the following warning from checkpatch.pl:
>
> WARNING: Missing a blank line after declarations
> + struct msdc_host *host = mmc_priv(mmc);
> + msdc_pm(state, (void *)host);
>
> Signed-off-by: Nícolas F. R. A. Prado <nfraprado@protonmail.com>
>
> ---
>
> Hi, this is my first commit. Let me know if there's anything I can do
> better.
> ---
> drivers/staging/mt7621-mmc/sd.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/staging/mt7621-mmc/sd.c b/drivers/staging/mt7621-mmc/sd.c
> index 0379f9c96..7b66f9b0a 100644
> --- a/drivers/staging/mt7621-mmc/sd.c
> +++ b/drivers/staging/mt7621-mmc/sd.c
> @@ -1797,6 +1797,7 @@ static void msdc_drv_pm(struct platform_device *pdev, pm_message_t state)
>
> if (mmc) {
> struct msdc_host *host = mmc_priv(mmc);
> +
> msdc_pm(state, (void *)host);
> }
This patch is fine, and I'll take it, but can't this be written a lot
simpler:
if (mmc)
msdc_pm(state, mmc_priv(mmc));
that looks better, don't you think?
thanks,
greg k-h
prev parent reply other threads:[~2018-11-07 12:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 0:42 [PATCH] staging: mt7621-mmc: Add blank line after declaration nicolas
2018-11-07 11:26 ` 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=20181107112650.GA29485@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=lkcamp@lists.libreplanetbr.org \
--cc=nicolas@autobyte.com.br \
--cc=pure.logic@nexus-software.ie \
/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