From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: vergilzhang <zhang_shurong@foxmail.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8192e: Change fixed function names with "%s: ", __func__
Date: Wed, 2 Aug 2017 11:02:26 -0700 [thread overview]
Message-ID: <20170802180226.GA7661@kroah.com> (raw)
In-Reply-To: <59821324.87ecca0a.2ff91.285fSMTPIN_ADDED_BROKEN@mx.google.com>
On Thu, Aug 03, 2017 at 01:59:56AM +0800, vergilzhang wrote:
> staging: rtl8192e: Fix coding style issue caught by checkpatch.pl related to function name in debug print
>
> Signed-off-by: vergilzhang <zhang_shurong@foxmail.com>
> ---
> drivers/staging/rtl8192e/dot11d.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
You didn't pay attention to the other issues my patch bot sent you about
this patch, why not? I'll just wait for you to fix them all and drop
this one for now, sorry.
greg k-h
next parent reply other threads:[~2017-08-02 18:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <59821324.87ecca0a.2ff91.285fSMTPIN_ADDED_BROKEN@mx.google.com>
2017-08-02 18:02 ` Greg Kroah-Hartman [this message]
[not found] <5982807a.09b46b0a.6bc9e.bddbSMTPIN_ADDED_BROKEN@mx.google.com>
2017-08-17 17:59 ` [PATCH] staging: rtl8192e: Change fixed function names with "%s: ", __func__ Greg Kroah-Hartman
2017-08-18 15:53 [PATCH] staging: rtl8192e: Change fixed function names with "%s: ",__func__ =?gb18030?B?1cXK98jZ?=
2017-08-20 18:12 ` [PATCH] staging: rtl8192e: Change fixed function names with "%s: ", __func__ Greg Kroah-Hartman
[not found] <20170821133235.GA10327@MarvinZhang.kernel@gmail.com>
2017-08-23 1:32 ` [PATCH] staging: rtl8192e: Change fixed function names with "%s:", __func__ Greg Kroah-Hartman
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=20170802180226.GA7661@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zhang_shurong@foxmail.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