From: Andrew Jeffery <andrew@aj.id.au>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Yong Li <sdliyong@gmail.com>, Joel Stanley <joel@jms.id.au>,
Arnd Bergmann <arnd@arndb.de>, Rick Altherr <raltherr@google.com>,
Rob Herring <robh@kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] pinctrl: aspeed: Fix ast2500 strap register write logic
Date: Wed, 23 Aug 2017 23:17:02 +0930 [thread overview]
Message-ID: <1503496022.7266.40.camel@aj.id.au> (raw)
In-Reply-To: <CACRpkdbBjfi-=oEu+pXgqy_kcVaP85Dy=C6_VnwNjBe89yXFMg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1489 bytes --]
On Wed, 2017-08-23 at 10:23 +0200, Linus Walleij wrote:
> > On Wed, Aug 23, 2017 at 1:54 AM, Andrew Jeffery <andrew@aj.id.au> wrote:
> > On Tue, 2017-08-22 at 14:52 +0200, Linus Walleij wrote:
> > > > > > > > On Tue, Aug 15, 2017 at 6:21 PM, Yong Li <sdliyong@gmail.com> wrote:
> > > > On AST2500, the hardware strap register(SCU70) only accepts write ‘1’,
> > > > to clear it to ‘0’, must set bits(write ‘1’) to SCU7C
> > > >
> > > > Signed-off-by: Yong Li <sdliyong@gmail.com>
> > >
> > > Patch applied with Andrew's review/test tags.
> >
> > I realised after I sent the tags on v3 that I'd made a mistake: There's a
> > slightly awkward to test bug in the v3 implementation. I followed up on v3 with
> > this:
> >
> > https://lkml.org/lkml/2017/8/16/905
> >
> > And Yong sent out a corresponding v4:
> >
> > https://patchwork.ozlabs.org/patch/802946/
>
> Ah. I got confused and picked the wrong version.
Entirely my fault. Apologies again for the confusion. I owe you a few drinks if
we ever meet :)
>
> > I see you've pushed Yong's v3 in pinctrl/devel - can we revert/remove that and
> > apply v4?
>
> No I would have to revert the patch.
>
> Can't we simply make a small fixup patch?
I couldn't recall what the rebase policy was for pinctrl/devel.
I have sent the fixup patch:
http://patchwork.ozlabs.org/patch/804981/
Cheers,
Andrew
>
> Yours,
> Linus Walleij
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
prev parent reply other threads:[~2017-08-23 13:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-15 16:21 [PATCH v3] pinctrl: aspeed: Fix ast2500 strap register write logic Yong Li
2017-08-16 13:45 ` Andrew Jeffery
2017-08-16 15:05 ` Yong Li
2017-08-17 3:19 ` Andrew Jeffery
2017-08-17 14:54 ` Yong Li
2017-08-22 12:52 ` Linus Walleij
2017-08-22 23:54 ` Andrew Jeffery
2017-08-23 8:23 ` Linus Walleij
2017-08-23 13:47 ` Andrew Jeffery [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=1503496022.7266.40.camel@aj.id.au \
--to=andrew@aj.id.au \
--cc=arnd@arndb.de \
--cc=joel@jms.id.au \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raltherr@google.com \
--cc=robh@kernel.org \
--cc=sdliyong@gmail.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;
as well as URLs for NNTP newsgroup(s).