From: Greg KH <gregkh@linuxfoundation.org>
To: Jesse Barton <jessebarton95@gmail.com>
Cc: valdis.kletnieks@vt.edu, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] Staging: exfat: exfat_super.c: fixed multiple coding style issues with camelcase and parentheses
Date: Sun, 29 Sep 2019 09:26:57 +0200 [thread overview]
Message-ID: <20190929072657.GB1879787@kroah.com> (raw)
In-Reply-To: <20190929002233.21998-1-jessebarton95@gmail.com>
On Sat, Sep 28, 2019 at 07:22:33PM -0500, Jesse Barton wrote:
> Fixed coding style issues with camelcase on functions and various parentheses that were not needed
Please wrap your changelog text properly.
Only do one "type" of thing per patch, this should be two different
ones.
thanks,
greg k-h
next prev parent reply other threads:[~2019-09-29 7:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-29 0:22 [PATCH 2/3] Staging: exfat: exfat_super.c: fixed multiple coding style issues with camelcase and parentheses Jesse Barton
2019-09-29 7:26 ` Greg KH [this message]
2019-10-01 13:18 ` Dan Carpenter
-- strict thread matches above, loose matches on Subject: below --
2019-09-29 14:52 Jesse Barton
2019-09-29 14:58 ` Greg KH
2019-10-01 13:28 ` Dan Carpenter
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=20190929072657.GB1879787@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=jessebarton95@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=valdis.kletnieks@vt.edu \
/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