From: Greg KH <gregkh@linuxfoundation.org>
To: Sushil Verma <sushil.bit.cse@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8192e: fix camelcase style warning
Date: Fri, 4 Jan 2019 09:36:00 +0100 [thread overview]
Message-ID: <20190104083600.GC25233@kroah.com> (raw)
In-Reply-To: <20181228122104.GA25322@localhost.localdomain>
On Fri, Dec 28, 2018 at 05:51:09PM +0530, Sushil Verma wrote:
> Remove CamelCase words. Warning found using checkpatch.pl
>
> Signed-off-by: Sushil Verma <sushil.bit.cse@gmail.com>
> ---
> drivers/staging/rtl8192e/dot11d.c | 84 +++++++++++++++----------------
> 1 file changed, 42 insertions(+), 42 deletions(-)
Please always use scripts/get_maintainer.pl to determine what people and
lists to send a patch to, as well as always test-build your changes
before sending them out :(
thanks,
greg k-h
prev parent reply other threads:[~2019-01-04 8:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-28 12:21 [PATCH] staging: rtl8192e: fix camelcase style warning Sushil Verma
2018-12-28 12:51 ` kbuild test robot
2019-01-04 8:36 ` 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=20190104083600.GC25233@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sushil.bit.cse@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