linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhang Rui <rui.zhang@intel.com>
To: Jacob Pan <jacob.jun.pan@linux.intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linux PM <linux-pm@vger.kernel.org>,
	stable@vger.kernel.org,
	Rafael Wysocki <rafael.j.wysocki@intel.com>
Subject: Re: [PATCH] thermal/powerclamp: add back module device table
Date: Mon, 21 Nov 2016 11:43:10 +0800	[thread overview]
Message-ID: <1479699790.2360.10.camel@intel.com> (raw)
In-Reply-To: <20161117114216.3fa995b4@jacob-builder>

On Thu, 2016-11-17 at 11:42 -0800, Jacob Pan wrote:
> On Tue, 15 Nov 2016 08:03:32 +0100
> Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> 
> > 
> > On Mon, Nov 14, 2016 at 11:08:45AM -0800, Jacob Pan wrote:
> > > 
> > > Commit 3105f234e0aba43e44e277c20f9b32ee8add43d4 replaced module
> > > cpu id table with a cpu feature check, which is logically
> > > correct.
> > > But we need the module device table to allow module auto loading.
> > > 
> > > Fixes:3105f234 thermal/powerclamp: correct cpu support check
> > > Signed-off-by: Jacob Pan <jacob.jun.pan@linux.intel.com>
> > > ---
> > >  drivers/thermal/intel_powerclamp.c | 9 ++++++++-
> > >  1 file changed, 8 insertions(+), 1 deletion(-)  
> > <formletter>
> > 
> > This is not the correct way to submit patches for inclusion in the
> > stable kernel tree.  Please read
> > Documentation/stable_kernel_rules.txt
> > for how to do this properly.
> > 
> > </formletter>
> Good to know, thanks. Rui will take care of it this time. Per Rui
> "I will apply patch 1 and queue up for next -rc and 4.8 stable."
> 

Just find another problem.
We're still missing this upstream
commit 3105f234e0aba43e44e277c20f9b32ee8add43d4 (thermal/powerclamp:
correct cpu support check) for 4.7 stable, and in this case, we can not
queue this patch for both 4.7 and 4.8 stable at the moment because it
does not apply to 4.7 stable.

I will send this patch out asap to catch 4.9, and then send a note to
stable kernel with the following Option 2
in Documentation/stable_kernel_rules.txt after it's merged.

thanks,
rui

  reply	other threads:[~2016-11-21  3:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-14 19:08 [PATCH] thermal/powerclamp: add back module device table Jacob Pan
2016-11-15  7:03 ` Greg Kroah-Hartman
2016-11-17 19:42   ` Jacob Pan
2016-11-21  3:43     ` Zhang Rui [this message]
2016-11-21  7:13       ` Greg Kroah-Hartman
2016-11-21 12:27         ` Zhang Rui
  -- strict thread matches above, loose matches on Subject: below --
2016-11-09 15:01 Jacob Pan
2016-11-09 15:08 ` Greg Kroah-Hartman
2016-11-14 19:09   ` Jacob Pan

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=1479699790.2360.10.camel@intel.com \
    --to=rui.zhang@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jacob.jun.pan@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=stable@vger.kernel.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).