From: NeilBrown <neil@brown.name>
To: Sankalp Negi <sankalpnegi2310@gmail.com>, gregkh@linuxfoundation.org
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
sankalpnegi2310@gmail.com
Subject: Re: [PATCH v2] staging: mt7621-mmc: Fix line size exceeding 80 columns
Date: Thu, 31 May 2018 08:08:55 +1000 [thread overview]
Message-ID: <87bmcwvls8.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <20180530190444.23006-1-sankalpnegi2310@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1040 bytes --]
On Thu, May 31 2018, Sankalp Negi wrote:
> This patch fixes checkpatch.pl warning and check:
> WARNING: line over 80 characters
> CHECK: Alignment should match open parenthesis
>
> Signed-off-by: Sankalp Negi <sankalpnegi2310@gmail.com>
Reviewed-by: NeilBrown <neil@brown.name>
Thanks,
NeilBrown
> ---
> Changes in v2:
> - Made alignments to match open parenthesis.
> ---
> drivers/staging/mt7621-mmc/dbg.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/staging/mt7621-mmc/dbg.c b/drivers/staging/mt7621-mmc/dbg.c
> index d897b1216348..6e4e223cddfb 100644
> --- a/drivers/staging/mt7621-mmc/dbg.c
> +++ b/drivers/staging/mt7621-mmc/dbg.c
> @@ -229,7 +229,8 @@ static int msdc_debug_proc_read(struct seq_file *s, void *p)
> }
>
> static ssize_t msdc_debug_proc_write(struct file *file,
> - const char __user *buf, size_t count, loff_t *data)
> + const char __user *buf,
> + size_t count, loff_t *data)
> {
> int ret;
>
> --
> 2.11.0
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2018-05-30 22:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 17:37 [PATCH] " Sankalp Negi
2018-05-29 21:57 ` NeilBrown
2018-05-30 19:04 ` [PATCH v2] " Sankalp Negi
2018-05-30 22:08 ` NeilBrown [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=87bmcwvls8.fsf@notabene.neil.brown.name \
--to=neil@brown.name \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sankalpnegi2310@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®