mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: llyyr <llyyr.public@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Jean Delvare <jdelvare@suse.com>,
	linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hwmon: (nct6683) Add another customer ID for NCT6687D sensor chip on some MSI boards.
Date: Fri, 19 May 2023 19:33:39 +0530	[thread overview]
Message-ID: <891d7a86-cab3-bbf3-89d3-6e521e5aef04@gmail.com> (raw)
In-Reply-To: <ca6da82a-c535-4d31-9657-01c6327c870a@roeck-us.net>

On 5/19/23 19:21, Guenter Roeck wrote:
> On Fri, May 19, 2023 at 07:16:53PM +0530, llyyr wrote:
>> On 5/19/23 18:23, Guenter Roeck wrote:
>>> On Wed, May 17, 2023 at 09:50:25AM +0530, Gopal Prasad wrote:
>>>> From: llyyr <llyyr.public@gmail.com>
>>>>
>>>
>>> The above is still wrong. Never mind, I fixed that.
>>
>> I wasn't sure about it, but I checked and I'm pretty sure pseudonyms are
>> allowed [1]. Is the problem here that my online handle not have a first name
>> and a last name part?
>>
>> * https://www.kernel.org/doc/html/v6.3/process/submitting-patches.html#developer-s-certificate-of-origin-1-1
>>
> 
> "... using a known identity (sorry, no anonymous contributions.)"
>                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
> Are you making that up ?
> 
> Guenter

Please see commit d4563201f33a022fc0353033d9dfeb1606a88330 [1] and DCO 
Guidelines [2]

 > And despite the language, we've always accepted nicknames and
that language was never meant to be any kind of exclusionary wording.


 > A real name does not require a legal name, nor a birth name, nor any 
name that appears on an official ID (e.g. a passport). Your real name is 
the name you convey to people in the community for them to use to 
identify you as you. The key concern is that your identification is 
sufficient enough to contact you if an issue were to arise in the future 
about your contribution.

* 
https://github.com/torvalds/linux/commit/d4563201f33a022fc0353033d9dfeb1606a88330
* https://github.com/cncf/foundation/blob/main/dco-guidelines.md

  parent reply	other threads:[~2023-05-19 14:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-17  4:20 Gopal Prasad
2023-05-19 12:53 ` Guenter Roeck
2023-05-19 13:46   ` llyyr
2023-05-19 13:51     ` Guenter Roeck
2023-05-19 13:53       ` llyyr
2023-05-19 14:03       ` llyyr [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-05-15 14:49 llyyr
2023-05-15 18:59 ` Guenter Roeck
2023-05-15 20:52   ` llyyr
2023-05-16 19:56     ` Guenter Roeck

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=891d7a86-cab3-bbf3-89d3-6e521e5aef04@gmail.com \
    --to=llyyr.public@gmail.com \
    --cc=jdelvare@suse.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    /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

all inboxes | Powered by JetHome®