From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Rafael Wysocki <rjw@rjwysocki.net>,
Lists linaro-kernel <linaro-kernel@lists.linaro.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cpufreq: acpi: Allow new dynamics attributes to be added to acpi_cpufreq_attr
Date: Wed, 16 Mar 2016 11:53:14 +0700 [thread overview]
Message-ID: <20160316045314.GD16250@vireshk-mac-ubuntu> (raw)
In-Reply-To: <CAJZ5v0i6Lv+-A4ZC3JOtr8FNcXYn1copS4C8oEmLrh+1eXT0MQ@mail.gmail.com>
On 09-03-16, 14:13, Rafael J. Wysocki wrote:
> On Wed, Mar 9, 2016 at 10:41 AM, Viresh Kumar <viresh.kumar@linaro.org> wrote:
> > On 03-03-16, 18:29, Rafael J. Wysocki wrote:
> >> Srinivas, can you please take this and rebase your patch on top of it?
> >> Or if you prefer, I can take it into my linux-next branch.
> >
> > Right, so you need to apply this patch as Srinivas already sent a separate patch
> > for his stuff, rebased over this.
>
> I know, but I'm deferring that one as we aren't entirely sure about
> the approach yet.
I might have missed, but what are we not sure about here ? I thought, all three
of us agreed that this is a good idea ..
--
viresh
next prev parent reply other threads:[~2016-03-16 4:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 19:13 [PATCH v4] cpufreq: acpi_cpufreq: base frequency attribute support Srinivas Pandruvada
2016-03-03 0:43 ` Rafael J. Wysocki
2016-03-03 3:04 ` Rafael J. Wysocki
2016-03-03 5:40 ` [PATCH] cpufreq: acpi: Allow new dynamics attributes to be added to acpi_cpufreq_attr Viresh Kumar
2016-03-03 17:29 ` Rafael J. Wysocki
2016-03-09 9:41 ` Viresh Kumar
2016-03-09 13:13 ` Rafael J. Wysocki
2016-03-16 4:53 ` Viresh Kumar [this message]
2016-03-16 12:30 ` Rafael J. Wysocki
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=20160316045314.GD16250@vireshk-mac-ubuntu \
--to=viresh.kumar@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.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).