From: Paul Bolle <pebolle@tiscali.nl>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] PM / OPP: Remove ARCH_HAS_OPP completely
Date: Fri, 12 Sep 2014 11:14:55 +0000 [thread overview]
Message-ID: <1410520495.31130.37.camel@x220> (raw)
In-Reply-To: <CAMuHMdUe+GKaYMmbC9JO=Qt7oNiEja0nGbp8oXVS=G4WJHmwJg@mail.gmail.com>
On Fri, 2014-09-12 at 13:03 +0200, Geert Uytterhoeven wrote:
> Hi Paul, Rafael,
>
> On Fri, Sep 12, 2014 at 12:46 PM, Paul Bolle <pebolle@tiscali.nl> wrote:
> >> > arch/arm/mach-shmobile/Kconfig | 1 -
> >> > drivers/devfreq/Kconfig | 1 -
> >
> > Were patches submitted for these two files too? If so, we can probably
> > just drop my patch.
>
> Rafael said: "I've queued this up for 3.17, thanks!"
>
> http://lists.infradead.org/pipermail/linux-arm-kernel/2014-July/274681.html
>
> But it's not in -next.
I think that patch landed as commit 78c5e0bb145d. But for some unknown
reason it didn't remove all selects statements for ARCH_HAS_OPP.
The odd thing here is that the last select statements I remove in this
patch are all to be found in Kconfig files that actually were touched in
that commit. Perhaps these select statements were merged back in during
conflict resolution. I have no idea.
Paul Bolle
next prev parent reply other threads:[~2014-09-12 11:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1406551632.5397.17.camel@x220>
2014-09-12 8:38 ` [PATCH] PM / OPP: Remove ARCH_HAS_OPP completely Paul Bolle
2014-09-12 10:20 ` Nishanth Menon
2014-09-12 10:46 ` Paul Bolle
2014-09-12 11:03 ` Geert Uytterhoeven
2014-09-12 11:14 ` Paul Bolle [this message]
2014-09-16 0:09 ` Simon Horman
2014-09-16 0:23 ` Simon Horman
2014-09-23 8:08 ` [PATCH] ARM: shmobile: " Paul Bolle
2014-09-23 8:27 ` Geert Uytterhoeven
2014-09-24 0:36 ` Simon Horman
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=1410520495.31130.37.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=linux-arm-kernel@lists.infradead.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).