From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Tawfik Bayouk <tawfik@marvell.com>,
Nadav Haklai <nadavh@marvell.com>,
Lior Amsalem <alior@marvell.com>,
Gregory Clement <gregory.clement@free-electrons.com>
Subject: Re: [PATCH] PM / OPP: Remove confusing error message in of_cpumask_init_opp_table()
Date: Wed, 14 Oct 2015 23:44:03 +0200 [thread overview]
Message-ID: <2736370.6HB7CanQEp@vostro.rjw.lan> (raw)
In-Reply-To: <20151014231039.1f62167c@free-electrons.com>
On Wednesday, October 14, 2015 11:10:39 PM Thomas Petazzoni wrote:
> Rafael,
>
> On Wed, 14 Oct 2015 23:28:51 +0200, Rafael J. Wysocki wrote:
>
> > > To avoid this confusion, this patch simply deletes the error message.
> > >
> > > Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> >
> > That's only present in linux-next now, right?
>
> No, it is already in 4.3-rc since 4.3-rc1. The commit adding the
> problematic function is 8d4d4e98acd68c31435ebb7beea591dbf60b9eb2, and
> this function gets used in cpufreq-dt starting at commit
> 2e02d8723edf6599988852a8ade8f83b2f766cb8.
>
> $ git tag --contains 2e02d8723edf6599988852a8ade8f83b2f766cb8
> v4.3-rc1
> v4.3-rc2
> v4.3-rc3
> v4.3-rc4
> v4.3-rc5
OK, thanks!
It should carry a
Fixes: 2e02d8723edf
tag then, right?
Thanks,
Rafael
next prev parent reply other threads:[~2015-10-14 21:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 15:52 [PATCH] PM / OPP: Remove confusing error message in of_cpumask_init_opp_table() Thomas Petazzoni
2015-10-14 21:28 ` Rafael J. Wysocki
2015-10-14 21:10 ` Thomas Petazzoni
2015-10-14 21:44 ` Rafael J. Wysocki [this message]
2015-10-14 21:29 ` Thomas Petazzoni
2015-10-14 21:59 ` Rafael J. Wysocki
2015-10-14 21:31 ` Thomas Petazzoni
2015-10-15 7:35 ` Viresh Kumar
2015-10-15 7:42 ` Thomas Petazzoni
2015-10-15 14:37 ` Viresh Kumar
2015-10-15 21:26 ` Rafael J. Wysocki
2015-10-16 5:39 ` Viresh Kumar
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=2736370.6HB7CanQEp@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=alior@marvell.com \
--cc=gregkh@linuxfoundation.org \
--cc=gregory.clement@free-electrons.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nadavh@marvell.com \
--cc=pavel@ucw.cz \
--cc=tawfik@marvell.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=viresh.kumar@linaro.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