From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Jan Kiszka <jan.kiszka@siemens.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH v13 1/2] serial: exar: split out the exar code from 8250_pci
Date: Mon, 06 Feb 2017 22:13:44 +0000 [thread overview]
Message-ID: <5898F518.3000402@gmail.com> (raw)
In-Reply-To: <1a0e4034-007e-d5cf-27ff-eb382ead776e@siemens.com>
On Monday 06 February 2017 01:49 PM, Jan Kiszka wrote:
> On 2017-02-03 22:31, Sudip Mukherjee wrote:
>> On Friday 03 February 2017 02:02 PM, Jan Kiszka wrote:
>>> BTW, are you personally the copyright holder or your employer Codethink?
>>> Depends on your contractual situation, but the former is less common.
>>
>> Well, Codethink has nothing to do with this patch. This was a voluntary
>> work started before I joined Codethink, but then I joined Codethink and
>> found very little time to finish this. So finally now its done.
>>
>> https://lists.kernelnewbies.org/pipermail/kernelnewbies/2015-November/015372.html
>>
>
> Hmm, why using your corporate email address then? This suggests a
> different copyright situation.
>
> Funnily, I just received this question internally: How can you tell
> apart if someone sends a personal contribution via his/her employer
> account from someone contributing on behalf of a company, thus with that
> company holding the rights? I argued that no one would do the former to
> prevent wrong accounting, but you just proved a counterexample. :)
well, I have been doing it this way from the very first day I started
contributing.
Regards
Sudip
next prev parent reply other threads:[~2017-02-06 22:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 22:28 [PATCH v13 1/2] serial: exar: split out the exar code from 8250_pci Sudip Mukherjee
2017-01-30 22:28 ` [PATCH v13 2/2] serial: 8250_pci: remove exar code Sudip Mukherjee
2017-02-03 14:02 ` [PATCH v13 1/2] serial: exar: split out the exar code from 8250_pci Jan Kiszka
2017-02-03 14:08 ` Andy Shevchenko
2017-02-03 21:31 ` Sudip Mukherjee
2017-02-04 14:51 ` Andy Shevchenko
2017-02-06 13:49 ` Jan Kiszka
2017-02-06 14:06 ` Greg Kroah-Hartman
2017-02-06 14:20 ` Jan Kiszka
2017-02-06 22:07 ` Sudip Mukherjee
2017-02-06 22:13 ` Sudip Mukherjee [this message]
2017-02-06 14:45 ` Jan Kiszka
2017-02-06 22:04 ` Sudip Mukherjee
2017-02-07 10:09 ` Jan Kiszka
2017-02-06 19:37 ` Jan Kiszka
2017-02-06 19:47 ` Jan Kiszka
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=5898F518.3000402@gmail.com \
--to=sudipm.mukherjee@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jan.kiszka@siemens.com \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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.