From: Greg KH <gregkh@linuxfoundation.org>
To: Arushi Singhal <arushisinghal19971997@gmail.com>
Cc: outreachy-kernel@googlegroups.com, devel@driverdev.osuosl.org,
linux-fbdev@vger.kernel.org, teddy.wang@siliconmotion.com,
linux-kernel@vger.kernel.org, sudipm.mukherjee@gmail.com
Subject: Re: [PATCH 0/3] staging: sm750fb: multiple checkpatch issues
Date: Sun, 12 Mar 2017 14:04:51 +0000 [thread overview]
Message-ID: <20170312140451.GC15102@kroah.com> (raw)
In-Reply-To: <20170311032410.8265-1-arushisinghal19971997@gmail.com>
On Sat, Mar 11, 2017 at 08:54:07AM +0530, Arushi Singhal wrote:
> Improve readability by fixing multiple checkpatch.pl
> issues in sm750fb driver.
>
> Arushi Singhal (3):
> staging: sm750fb: function prototype argument should have an
> identifier name
> staging: sm750fb: fixes add blank line after
> function/struct/union/enum declarations
> staging: sm750fb: Alignment should match open parenthesis
This is a v2 series, right? Please always say so. Otherwise I'm going
to drop it from my queue, like I just did :(
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Arushi Singhal <arushisinghal19971997@gmail.com>
Cc: outreachy-kernel@googlegroups.com, devel@driverdev.osuosl.org,
linux-fbdev@vger.kernel.org, teddy.wang@siliconmotion.com,
linux-kernel@vger.kernel.org, sudipm.mukherjee@gmail.com
Subject: Re: [PATCH 0/3] staging: sm750fb: multiple checkpatch issues
Date: Sun, 12 Mar 2017 15:04:51 +0100 [thread overview]
Message-ID: <20170312140451.GC15102@kroah.com> (raw)
In-Reply-To: <20170311032410.8265-1-arushisinghal19971997@gmail.com>
On Sat, Mar 11, 2017 at 08:54:07AM +0530, Arushi Singhal wrote:
> Improve readability by fixing multiple checkpatch.pl
> issues in sm750fb driver.
>
> Arushi Singhal (3):
> staging: sm750fb: function prototype argument should have an
> identifier name
> staging: sm750fb: fixes add blank line after
> function/struct/union/enum declarations
> staging: sm750fb: Alignment should match open parenthesis
This is a v2 series, right? Please always say so. Otherwise I'm going
to drop it from my queue, like I just did :(
thanks,
greg k-h
next prev parent reply other threads:[~2017-03-12 14:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-11 3:24 [PATCH 0/3] staging: sm750fb: multiple checkpatch issues Arushi Singhal
2017-03-11 3:36 ` Arushi Singhal
2017-03-11 3:24 ` [PATCH 1/3] staging: sm750fb: function prototype argument should have an identifier name Arushi Singhal
2017-03-11 3:36 ` Arushi Singhal
2017-03-11 6:49 ` [Outreachy kernel] [PATCH 1/3] staging: sm750fb: function prototype argument should have an iden Julia Lawall
2017-03-11 6:49 ` [Outreachy kernel] [PATCH 1/3] staging: sm750fb: function prototype argument should have an identifier name Julia Lawall
2017-03-11 3:24 ` [PATCH 2/3] staging: sm750fb: fixes add blank line after function/struct/union/enum declarations Arushi Singhal
2017-03-11 3:36 ` Arushi Singhal
2017-03-11 3:24 ` [PATCH 3/3] staging: sm750fb: Alignment should match open parenthesis Arushi Singhal
2017-03-11 3:36 ` Arushi Singhal
2017-03-11 6:48 ` [Outreachy kernel] " Julia Lawall
2017-03-11 6:48 ` Julia Lawall
2017-03-12 14:04 ` Greg KH [this message]
2017-03-12 14:04 ` [PATCH 0/3] staging: sm750fb: multiple checkpatch issues Greg KH
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=20170312140451.GC15102@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arushisinghal19971997@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=outreachy-kernel@googlegroups.com \
--cc=sudipm.mukherjee@gmail.com \
--cc=teddy.wang@siliconmotion.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.