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] multiple checkpatch issues
Date: Fri, 10 Mar 2017 22:05:33 +0000 [thread overview]
Message-ID: <20170310220533.GA19329@kroah.com> (raw)
In-Reply-To: <20170310215657.7069-1-arushisinghal19971997@gmail.com>
On Sat, Mar 11, 2017 at 03:26:54AM +0530, Arushi Singhal wrote:
> Improve readability by fixing multiple checkpatch.pl
> issues in sm750fb driver.
Note, _PLEASE_ put the subsystem/driver name in this 0/X email subject
line, like your patches have them. It makes it easier when I sort
patches by driver/subsystem when reviewing them. As it is, I end up
always ignoring these 0/X emails.
thanks,
greg k-h
prev parent reply other threads:[~2017-03-10 22:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-05 11:36 [PATCH 0/3] multiple checkpatch issues Arushi Singhal
2017-03-05 11:36 ` [PATCH 1/3] staging: sm750fb: fixes add blank line after function/struct/union/enum declarations Arushi Singhal
2017-03-06 19:34 ` Geert Uytterhoeven
2017-03-07 17:39 ` Dan Carpenter
2017-03-05 11:36 ` [PATCH 2/3] staging: sm750fb: function prototype argument should have an identifier name Arushi Singhal
2017-03-05 11:36 ` [PATCH 3/3] staging: sm750fb: Alignment should match open parenthesis Arushi Singhal
2017-03-07 17:44 ` Dan Carpenter
2017-03-05 13:39 ` [PATCH 0/3] multiple checkpatch issues Joe Perches
2017-03-10 21:57 ` Arushi Singhal
2017-03-10 21:57 ` [PATCH 1/3] staging: sm750fb: function prototype argument should have an identifier name Arushi Singhal
2017-03-10 21:57 ` [PATCH 2/3] staging: sm750fb: fixes add blank line after function/struct/union/enum declarations Arushi Singhal
2017-03-10 21:58 ` [PATCH 3/3] staging: sm750fb: Alignment should match open parenthesis Arushi Singhal
2017-03-10 22:05 ` 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=20170310220533.GA19329@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).