All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Diego Elio Pettenò" <flameeyes@flameeyes.eu>
Cc: stable@vger.kernel.org, Johan Hovold <johan@kernel.org>
Subject: Re: Request for inclusion in stable of 4307413256ac1e09b8f53e8715af3df9e49beec3
Date: Mon, 8 Jan 2018 08:54:25 +0100	[thread overview]
Message-ID: <20180108075425.GD24062@kroah.com> (raw)
In-Reply-To: <CAHcsgXTFt6hy05OYR-EP1OJ1JZn66J2eoJx0CpTYxvXnftKP3A@mail.gmail.com>

On Sun, Jan 07, 2018 at 11:51:14AM +0000, Diego Elio Petten� wrote:
> On Sun, Jan 7, 2018 at 8:15 AM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > Patches have to be in Linus's tree before they can be accepted into any
> > stable kernel release, please read:
> >     https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
> > for the rules of all of this.
> 
> I was hoping rules could be bent a bit, since this is a single device
> ID, and the timing (both in the -rc cycle and with KPTI) makes it
> particularly awkward O:)

A single device id is not worth breaking the rules for, sorry.

You are going to be updating your kernel a bunch more times over the
next months, due to all of this mess, this id will trickle in at
sometime during all of that, don't worry...

greg k-h

      reply	other threads:[~2018-01-08  7:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-06 19:44 Request for inclusion in stable of 4307413256ac1e09b8f53e8715af3df9e49beec3 Diego Elio Pettenò
2018-01-07  8:15 ` Greg KH
2018-01-07 11:51   ` Diego Elio Pettenò
2018-01-08  7:54     ` Greg KH [this message]

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=20180108075425.GD24062@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=flameeyes@flameeyes.eu \
    --cc=johan@kernel.org \
    --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 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.