From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "SF Markus Elfring" <elfring@users.sourceforge.net>,
"USB list" <linux-usb@vger.kernel.org>,
"Alan Stern" <stern@rowland.harvard.edu>,
"Eugene Korenevsky" <ekorenevsky@gmail.com>,
"Günter Röck" <linux@roeck-us.net>,
"Jaejoong Kim" <climbbb.kim@gmail.com>,
"Johan Hovold" <johan@kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Mathias Nyman" <mathias.nyman@linux.intel.com>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>
Subject: Re: [PATCH] USB: core: Improve unlocking of a mutex in two functions
Date: Sun, 5 Nov 2017 08:30:13 +0100 [thread overview]
Message-ID: <20171105073013.GA1431@kroah.com> (raw)
In-Reply-To: <CAMuHMdUXn4YVPBFCoqmwcdU7eTWO5jy2ZXZQaAxPi1P5bM4q2A@mail.gmail.com>
On Sun, Nov 05, 2017 at 12:25:19AM +0100, Geert Uytterhoeven wrote:
> On Sat, Nov 4, 2017 at 9:12 PM, SF Markus Elfring
> <elfring@users.sourceforge.net> wrote:
> > From: Markus Elfring <elfring@users.sourceforge.net>
> > Date: Sat, 4 Nov 2017 21:00:46 +0100
> >
> > * Add jump targets so that a call of the function "mutex_unlock" is stored
> > only twice in these function implementations.
> >
> > * Replace five calls by goto statements.
> >
> > This issue was detected by using the Coccinelle software.
> >
> > Signed-off-by: Markus Elfring <elfring@users.sourceforge.net>
>
> NAKed-by: Geert Uytterhoeven <geert@linux-m68k.org>
Don't worry, or waste your time, I don't take patches from this author
as they are in my blacklist.
greg k-h
next prev parent reply other threads:[~2017-11-05 7:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-04 20:12 [PATCH] USB: core: Improve unlocking of a mutex in two functions SF Markus Elfring
2017-11-04 23:25 ` Geert Uytterhoeven
2017-11-05 7:30 ` Greg Kroah-Hartman [this message]
2017-11-05 9:33 ` SF Markus Elfring
2017-11-05 8:29 ` [PATCH] " SF Markus Elfring
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=20171105073013.GA1431@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=climbbb.kim@gmail.com \
--cc=corbet@lwn.net \
--cc=ekorenevsky@gmail.com \
--cc=elfring@users.sourceforge.net \
--cc=geert@linux-m68k.org \
--cc=johan@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mathias.nyman@linux.intel.com \
--cc=mchehab@kernel.org \
--cc=stern@rowland.harvard.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