From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Alex Manoussakis <amanou@gnu.org>
Cc: stable@vger.kernel.org, Jiri Kosina <jikos@kernel.org>,
Diego Elio Petteo <flameeyes@flameeyes.eu>
Subject: Re: [PATCH v1] HID: hid-elecom: extend to fix descriptor for HUGE trackball
Date: Tue, 17 Oct 2017 10:35:44 +0200 [thread overview]
Message-ID: <20171017083544.GA7128@kroah.com> (raw)
In-Reply-To: <20171017082559.GA19402@gnu.org>
On Tue, Oct 17, 2017 at 04:25:59AM -0400, Alex Manoussakis wrote:
> > > * Copyright (c) 2010 Richard Nauber <Richard.Nauber@gmail.com>
> > > * Copyright (c) 2016 Yuxuan Shui <yshuiv7@gmail.com>
> > > * Copyright (c) 2017 Diego Elio Petten� <flameeyes@flameeyes.eu>
> > > + * Copyright (c) 2017 Alex Manoussakis <amanou@gnu.org>
> >
> > Note, I'm not the maintainer, but you should be aware that adding a line
> > like this, with only the changes as expressed in this patch, is very
> > dubious according to every lawyer that I know. Please be careful about
> > stuff like this, and only add such a line if you really know what you
> > are doing[1]
> >
> > If you have done other changes to this file, my appologies...
>
> Hi Greg, thanks for the note. The changes I have done is add new USB IDs and
> change the text in a couple of places (both comments and messages) to include
> the new model "HUGE" where it only said "DEFT".
>
> We could remove the copyright line I added if it's a problem. I didn't give it
> much thought. I copied the linux-input maintainer Jiri, and Diego who added the
> code for the DEFT trackballs, in my mainline submission and both were ok
> (Diego wrote me "The patch looks good to me", and Jiri submitted it) and now
> it's in mainline. Copying Diego in this thread now too.
>
> My goal is simply to make the trackball I purchased work in my favorite OS,
> and benefit other users who have found or will find themselves with a semi-
> working device otherwise. And push as far back as 4.4 since some very popular
> long-term-support distros use this kernel, I use it too, and it works.
>
> Can you commit the patch upstream ? Below is the patch that will apply clean
> to 4.4 and 4.9, without the extra copyright line if you prefer to use that.
> Note 4.4 and 4.9 need to cherry pick 0bb7a37f8d15e5fb5d21776875f9fbc74e10753a
> as a prerequisite which adds support for the DEFT trackballs.
>
> Should I submit a mainline patch that removes the Copyright line I added ?
> Let me know what I should do and I'll be happy to do it.
Ok, if this is already merged, that's fine, just wanted to point out the
obvious copyright statement issues :)
I'll add it to my queue of patches to apply to as stable tree after
these next kernels get released, thanks.
greg k-h
next prev parent reply other threads:[~2017-10-17 8:35 UTC|newest]
Thread overview: 10+ 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 [this message]
2017-10-19 9:35 ` Greg Kroah-Hartman
2017-10-19 11:07 ` Jiri Kosina
2017-10-19 12:53 ` Greg Kroah-Hartman
2017-10-19 13:44 ` Alex Manoussakis
-- strict thread matches above, loose matches on Subject: below --
2017-10-05 17:41 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=20171017083544.GA7128@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=amanou@gnu.org \
--cc=flameeyes@flameeyes.eu \
--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 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.