From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Daniele Nicolodi <daniele@grinta.net>
Cc: SF Markus Elfring <elfring@users.sourceforge.net>,
kernel-janitors@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>,
Dan Carpenter <dan.carpenter@oracle.com>,
LKML <linux-kernel@vger.kernel.org>,
Jonathan Cameron <jic23@kernel.org>,
Samu Onkalo <samu.p.onkalo@nokia.com>
Subject: Re: [PATCH] misc: bh1770glc: Use common error handling code in bh1770_power_state_store()
Date: Fri, 27 Oct 2017 17:23:04 +0000 [thread overview]
Message-ID: <20171027172304.GA18401@kroah.com> (raw)
In-Reply-To: <9c0b957a-93b5-39c9-f9bd-cb754d009d62@grinta.net>
On Fri, Oct 27, 2017 at 11:11:13AM -0600, Daniele Nicolodi wrote:
> On 10/27/17 10:20 AM, SF Markus Elfring wrote:
> > From: Markus Elfring <elfring@users.sourceforge.net>
> > Date: Fri, 27 Oct 2017 18:00:31 +0200
> >
> > Adjust jump targets so that a bit of exception handling can be better
> > reused in an if branch of this function.
>
> What is the benefit brought by this change?
Please note, you are responding to someone who lots and lots of kernel
maintainers/developers have blacklisted, myself included. It's just not
worth your effort, I recommend doing the same, as I'm not applying any
patches from this author, unless some other maintainer wants to take the
time to validate and send them on to me.
kill-files are a good thing, please use them :)
good luck!
greg k-h
next prev parent reply other threads:[~2017-10-27 17:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 16:20 [PATCH] misc: bh1770glc: Use common error handling code in bh1770_power_state_store() SF Markus Elfring
2017-10-27 17:11 ` Daniele Nicolodi
2017-10-27 17:23 ` Greg Kroah-Hartman [this message]
2017-10-27 18:04 ` 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=20171027172304.GA18401@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=dan.carpenter@oracle.com \
--cc=daniele@grinta.net \
--cc=elfring@users.sourceforge.net \
--cc=jic23@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=samu.p.onkalo@nokia.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