From: "Jiejing.Zhang " <kzjeef@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Brian Foster <brian.foster@maxim-ic.com>,
Zhang Jiejing <jiejing.zhang@freescale.com>,
Joonyoung Shim <jy0922.shim@samsung.com>,
linux-input@vger.kernel.org,
Jean-Marc Simohand <JeanMarc.Simohand@maxim-ic.com>
Subject: Re: [Q] max11801 licensing terms
Date: Thu, 18 Aug 2011 18:27:10 +0800 [thread overview]
Message-ID: <CACrgxGD3M-yCSBdu3p9em698jQ4X2cZd17gHDYdvJWgFNG=PBg@mail.gmail.com> (raw)
In-Reply-To: <20110817174510.GF4877@core.coreip.homeip.net>
Hi Dmitry,
I've send a patch to mail list.
Thanks.
Best regards,
Zhang Jiejing
2011/8/18 Dmitry Torokhov <dmitry.torokhov@gmail.com>:
> On Wed, Aug 17, 2011 at 09:24:32PM +0800, Jiejing.Zhang wrote:
>> Hi Brian Foster,
>>
>> > * Based on mcs5000_ts.c
>> I have referenced mcs5000_ts.c source code when writing this driver,
>> but I don't think it's a big deal, I really reference lots of files.
>>
>> > What does “either version 2 of the License.” mean?
>> > Either GPLv2 or what?
>>
>> Yes, I think it means GPLv2, I'm not really not very care about these
>> license, just copy other files under driver/input/ directory.
>
> mcs5000_ts.c (and m97xx-core.c it was derived from) are GPLv2 or later
> so max11801_ts.c shoudl folow the same licensing terms, but it seems the
> statement was truncated.
>
> Jiejing, could you please send me a patch restoring the proper wording
> so there won't be any confusion in the future?
>
> Thanks!
>
> --
> Dmitry
>
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-08-18 10:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-17 12:31 [Q] max11801 licensing terms Brian Foster
2011-08-17 13:24 ` Jiejing.Zhang
2011-08-17 17:45 ` Dmitry Torokhov
2011-08-18 10:27 ` Jiejing.Zhang [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='CACrgxGD3M-yCSBdu3p9em698jQ4X2cZd17gHDYdvJWgFNG=PBg@mail.gmail.com' \
--to=kzjeef@gmail.com \
--cc=JeanMarc.Simohand@maxim-ic.com \
--cc=brian.foster@maxim-ic.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jiejing.zhang@freescale.com \
--cc=jy0922.shim@samsung.com \
--cc=linux-input@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).