Request for inclusion in stable of 4307413256ac1e09b8f53e8715af3df9e49beec3

Request for inclusion in stable of 4307413256ac1e09b8f53e8715af3df9e49beec3

[Diego Elio Pettenò]

Hi Greg, if possible I would like to ask for commit
4307413256ac1e09b8f53e8715af3df9e49beec3
(https://git.kernel.org/pub/scm/linux/kernel/git/johan/usb-serial.git/commit/?h=usb-linus&id=4307413256ac1e09b8f53e8715af3df9e49beec3
— "USB: serial: cp210x: add IDs for LifeScan OneTouch Verio IQ") to be
included in the next stable kernel(s).

It's a one line change that would save me a few headaches to not have
to build my own kernel just to get the driver loaded for this device
(for which I'm writing a tool) and will let users of the meter use the
tool sooner rather than later in the future.

Thanks!

-- 
Diego Elio Pettenò — Flameeyes
https://blog.flameeyes.eu/

Re: Request for inclusion in stable of 4307413256ac1e09b8f53e8715af3df9e49beec3

[Greg KH]

On Sat, Jan 06, 2018 at 07:44:37PM +0000, Diego Elio Pettenò wrote:
> Hi Greg, if possible I would like to ask for commit
> 4307413256ac1e09b8f53e8715af3df9e49beec3
> (https://git.kernel.org/pub/scm/linux/kernel/git/johan/usb-serial.git/commit/?h=usb-linus&id=4307413256ac1e09b8f53e8715af3df9e49beec3
> — "USB: serial: cp210x: add IDs for LifeScan OneTouch Verio IQ") to be
> included in the next stable kernel(s).
> 
> It's a one line change that would save me a few headaches to not have
> to build my own kernel just to get the driver loaded for this device
> (for which I'm writing a tool) and will let users of the meter use the
> tool sooner rather than later in the future.

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.

thanks,

greg k-h

Re: Request for inclusion in stable of 4307413256ac1e09b8f53e8715af3df9e49beec3

[Diego Elio Pettenò]

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:)

I'll take no for an answer, but I thought I would at least raise the comment.

Re: Request for inclusion in stable of 4307413256ac1e09b8f53e8715af3df9e49beec3

[Greg KH]

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