From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jiri Kosina <jikos@kernel.org>
Cc: Alex Manoussakis <amanou@gnu.org>, stable@vger.kernel.org
Subject: Re: [PATCH v1] HID: hid-elecom: extend to fix descriptor for HUGE trackball
Date: Thu, 19 Oct 2017 14:53:23 +0200 [thread overview]
Message-ID: <20171019125323.GA31847@kroah.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.1710191305200.9294@jbgna.fhfr.qr>
On Thu, Oct 19, 2017 at 01:07:25PM +0200, Jiri Kosina wrote:
> On Thu, 19 Oct 2017, Greg Kroah-Hartman wrote:
>
> > > Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > > Cc: <stable@stable@vger.kernel.org> # 4.12.x
> > > Cc: <stable@stable@vger.kernel.org> # 4.9.x: 0bb7a37: HID: elecom: ... DEFT trackballs
> > > Cc: <stable@stable@vger.kernel.org> # 4.4.x: 0bb7a37: HID: elecom: ... DEFT trackballs
> >
> > Commit 0bb7a37 is a "new feature", and as such, shouldn't be backported
> > to older kernels, right?
> >
> > I need a very strong agrument from the HID maintainer as to why this
> > should be accepted to the older kernels...
>
> Hi Greg,
>
> it basically is a new device ID addition (with a small glue code applied
> only to that device ID), and as such a left the stable markers there. But
> I don't have strong preference either way -- if you feel that this is
> beyond the 'new device ID' policy, I wouldn't object strongly.
I think it's a bit more than just the normal "add a new id or quirk"
logic here.
For new devices, it's always best to just update to a newer kernel,
there's no reason anyone with these devices should be using 4.9 or older
:)
thanks,
greg k-h
next prev parent reply other threads:[~2017-10-19 12:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-14 3:23 [PATCH v1] HID: hid-elecom: extend to fix descriptor for HUGE trackball Alex Manoussakis
2017-10-16 20:20 ` Alex Manoussakis
2017-10-17 6:58 ` Greg Kroah-Hartman
2017-10-17 8:25 ` Alex Manoussakis
2017-10-17 8:35 ` Greg Kroah-Hartman
2017-10-19 9:35 ` Greg Kroah-Hartman
2017-10-19 11:07 ` Jiri Kosina
2017-10-19 12:53 ` Greg Kroah-Hartman [this message]
2017-10-19 13:44 ` Alex Manoussakis
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=20171019125323.GA31847@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=amanou@gnu.org \
--cc=jikos@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 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).