From: Greg KH <gregkh@linuxfoundation.org>
To: Phil Reid <preid@electromag.com.au>
Cc: linus.walleij@linaro.org, stable@vger.kernel.org
Subject: Re: [PATCH 0/2] gpio: pca953x: Backported patches for 4.8
Date: Tue, 22 Nov 2016 09:02:21 +0100 [thread overview]
Message-ID: <20161122080221.GA7975@kroah.com> (raw)
In-Reply-To: <1479782086-96719-1-git-send-email-preid@electromag.com.au>
On Tue, Nov 22, 2016 at 10:34:44AM +0800, Phil Reid wrote:
> The following two patches should apply to the 4.8 branch.
>
> checkpatch complained about the commit reference format but looking at other
> patches in the 4.8 history I see some like this with the full id.
> So I'm not exactly sure if I've done this correctly.
Looks great to me, thanks for doing this.
greg k-h
prev parent reply other threads:[~2016-11-22 8:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 2:34 [PATCH 0/2] gpio: pca953x: Backported patches for 4.8 Phil Reid
2016-11-22 2:34 ` [PATCH 1/2] gpio: pca953x: Move memcpy into mutex lock for set multiple Phil Reid
2016-11-22 2:34 ` [PATCH 2/2] gpio: pca953x: Fix corruption of other gpios in set_multiple Phil Reid
2016-11-22 8:02 ` 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=20161122080221.GA7975@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=preid@electromag.com.au \
--cc=stable@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).