All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Winkler, Tomas" <tomas.winkler@intel.com>
Cc: "arnd@arndb.de" <arnd@arndb.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [char-misc-next] mei: add 9 series PCH mei device ids
Date: Thu, 5 Dec 2013 09:46:15 -0800	[thread overview]
Message-ID: <20131205174615.GA7383@kroah.com> (raw)
In-Reply-To: <5B8DA87D05A7694D9FA63FD143655C1B1AF24D4C@HASMSX106.ger.corp.intel.com>

On Thu, Dec 05, 2013 at 04:50:00PM +0000, Winkler, Tomas wrote:
> 
> 
> > On Thu, Dec 05, 2013 at 09:34:44AM +0200, Tomas Winkler wrote:
> > > And Lynx Point H Refresh and Wildcat Point LP
> > > device ids.
> > >
> > > Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
> > > ---
> > > V2: remove duplicated  LPT entry
> > >
> > >  drivers/misc/mei/hw-me-regs.h | 5 ++++-
> > >  drivers/misc/mei/pci-me.c     | 4 +++-
> > >  2 files changed, 7 insertions(+), 2 deletions(-)
> > 
> > This should go into 3.13-final, right?  What about -stable versions?
> 
> Yes, this can go to stable as well. I need to dig bit in from which
> version this is relevant, I think 3.9 and up
> I will resend with info.
> Can you just clarify for me what is the policy here, is the support
> for new HW a stable candidate?

Please read Documentation/stable_kernel_rules.txt for the stable rules.


  reply	other threads:[~2013-12-05 17:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-05  7:34 [char-misc-next] mei: add 9 series PCH mei device ids Tomas Winkler
2013-12-05 14:31 ` Greg KH
2013-12-05 16:50   ` Winkler, Tomas
2013-12-05 17:46     ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-12-03 11:01 Tomas Winkler
2013-12-05  4:19 ` Greg KH
2013-12-05  7:34   ` Winkler, Tomas

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=20131205174615.GA7383@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tomas.winkler@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 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.