From: Thierry Reding <treding@nvidia.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-gpio@vger.kernel.org
Subject: Re: [PATCH] pinctrl: bcm2835: Fix some merge fallout
Date: Thu, 9 Nov 2017 11:05:56 +0100 [thread overview]
Message-ID: <20171109100556.GA20678@ulmo> (raw)
In-Reply-To: <20171109083710.3567-1-linus.walleij@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 583 bytes --]
On Thu, Nov 09, 2017 at 09:37:10AM +0100, Linus Walleij wrote:
> Fixing a small merge problem in BCM2835 related to the
> new irqchip code.
>
> Cc: Thierry Reding <treding@nvidia.com>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> drivers/pinctrl/bcm/pinctrl-bcm2835.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
I was just going to send out a fixup for this as well. Looks like this
may be the result of the conflict that I had mentioned.
Anyway, not that you really need it, but:
Reviewed-by: Thierry Reding <treding@nvidia.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-11-09 10:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 8:37 [PATCH] pinctrl: bcm2835: Fix some merge fallout Linus Walleij
2017-11-09 10:05 ` Thierry Reding [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=20171109100556.GA20678@ulmo \
--to=treding@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@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