From: Jean Delvare <jdelvare@suse.de>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org
Subject: Re: [PATCH] Revert "pinctrl: amd: make it explicitly non-modular"
Date: Wed, 20 Jul 2016 23:13:10 +0200 [thread overview]
Message-ID: <20160720231310.28c6e0a2@endymion> (raw)
In-Reply-To: <20160719134439.GJ21225@windriver.com>
Hi Paul,
On Tue, 19 Jul 2016 09:44:40 -0400, Paul Gortmaker wrote:
> [Re: [PATCH] Revert "pinctrl: amd: make it explicitly non-modular"] On 19/07/2016 (Tue 10:46) Jean Delvare wrote:
> > On Mon, 18 Jul 2016 20:30:30 -0400, Paul Gortmaker wrote:
> > > This reverts commit b8c2b10a9bc0272a20e096852f8fbbf361749dda.
> > >
> > > This patch was in my queue at the same time that a conversion of
> > > the same driver from bool --> tristate was pending and merged.
> > >
> > > That is commit 337ea0fb1535 ("pinctrl: Turn AMD support to tristate")
> >
> > I can't find this commit anywhere, but I would certainly prefer this to
> > making the driver non-modular. So I vote in favor of this revert.
>
> It is a mainline commit, so I guess you need to pull in the last couple
> months of commits...
Oops, my bad, I was expecting something a lot more recent.
>
> paul@builder-02:~/git/linux-head$ git describe --contains 337ea0fb1535
> v4.6-rc1~149^2~35
> paul@builder-02:~/git/linux-head$ git show v4.6-rc1~149
> commit 5ca5446ec5ba5e79a6f271cd026bb153d6850fcc
> Merge: 710d60cbf1b3 3c177a166253
> Author: Linus Torvalds <torvalds@linux-foundation.org>
> Date: Tue Mar 15 20:23:13 2016 -0700
>
> Merge tag 'pinctrl-v4.6-1' of
> git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl
>
> Pull pin control updates from Linus Walleij:
Ah ah, now I see the commit is from me. How is it possible to have such
bad memory :*D
> I didn't bother marking it for 4.6 stable since it used to be builtin
> only and even with the crossed patches, it still would have been builtin;
> it just wouldn't respect the newly available tristate option if chosen.
I agree, it's no stable material. I'm happy it's finally sorted out,
thanks.
--
Jean Delvare
SUSE L3 Support
WARNING: multiple messages have this Message-ID (diff)
From: Jean Delvare <jdelvare@suse.de>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: <linux-kernel@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
<linux-gpio@vger.kernel.org>
Subject: Re: [PATCH] Revert "pinctrl: amd: make it explicitly non-modular"
Date: Wed, 20 Jul 2016 23:13:10 +0200 [thread overview]
Message-ID: <20160720231310.28c6e0a2@endymion> (raw)
In-Reply-To: <20160719134439.GJ21225@windriver.com>
Hi Paul,
On Tue, 19 Jul 2016 09:44:40 -0400, Paul Gortmaker wrote:
> [Re: [PATCH] Revert "pinctrl: amd: make it explicitly non-modular"] On 19/07/2016 (Tue 10:46) Jean Delvare wrote:
> > On Mon, 18 Jul 2016 20:30:30 -0400, Paul Gortmaker wrote:
> > > This reverts commit b8c2b10a9bc0272a20e096852f8fbbf361749dda.
> > >
> > > This patch was in my queue at the same time that a conversion of
> > > the same driver from bool --> tristate was pending and merged.
> > >
> > > That is commit 337ea0fb1535 ("pinctrl: Turn AMD support to tristate")
> >
> > I can't find this commit anywhere, but I would certainly prefer this to
> > making the driver non-modular. So I vote in favor of this revert.
>
> It is a mainline commit, so I guess you need to pull in the last couple
> months of commits...
Oops, my bad, I was expecting something a lot more recent.
>
> paul@builder-02:~/git/linux-head$ git describe --contains 337ea0fb1535
> v4.6-rc1~149^2~35
> paul@builder-02:~/git/linux-head$ git show v4.6-rc1~149
> commit 5ca5446ec5ba5e79a6f271cd026bb153d6850fcc
> Merge: 710d60cbf1b3 3c177a166253
> Author: Linus Torvalds <torvalds@linux-foundation.org>
> Date: Tue Mar 15 20:23:13 2016 -0700
>
> Merge tag 'pinctrl-v4.6-1' of
> git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl
>
> Pull pin control updates from Linus Walleij:
Ah ah, now I see the commit is from me. How is it possible to have such
bad memory :*D
> I didn't bother marking it for 4.6 stable since it used to be builtin
> only and even with the crossed patches, it still would have been builtin;
> it just wouldn't respect the newly available tristate option if chosen.
I agree, it's no stable material. I'm happy it's finally sorted out,
thanks.
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2016-07-20 21:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 0:30 [PATCH] Revert "pinctrl: amd: make it explicitly non-modular" Paul Gortmaker
2016-07-19 0:30 ` Paul Gortmaker
2016-07-19 8:46 ` Jean Delvare
2016-07-19 8:46 ` Jean Delvare
2016-07-19 13:44 ` Paul Gortmaker
2016-07-19 13:44 ` Paul Gortmaker
2016-07-20 21:13 ` Jean Delvare [this message]
2016-07-20 21:13 ` Jean Delvare
2016-07-22 15:27 ` Linus Walleij
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=20160720231310.28c6e0a2@endymion \
--to=jdelvare@suse.de \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.