From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Nechita, Ramona" <Ramona.Nechita@analog.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Cc: Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
"Hennerich, Michael" <Michael.Hennerich@analog.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: iio: adc: add a7779 doc
Date: Fri, 31 May 2024 09:45:25 +0200 [thread overview]
Message-ID: <ef601549-47a2-49cd-9c9c-1ea35ac7c1ee@kernel.org> (raw)
In-Reply-To: <SN6PR03MB4320A1D0DDCFBEED28319815F3F22@SN6PR03MB4320.namprd03.prod.outlook.com>
On 29/05/2024 17:25, Nechita, Ramona wrote:
> Hello,
>
> Thank you for your review. I will send a v2 shortly, I just have a minor misunderstanding below. I will send a v2 shortly without the clock-names.
>
>> On 22/05/2024 14:01, ranechita wrote:
>>> Add dt bindings for adc ad7779.
>>>
>>> Signed-off-by: ranechita <ramona.nechita@analog.com>
>>
>> Are you sure that's the name or identity you want to use? Looks like misconfigured git...
>
> Do you mean the email sign-off? Or just the name? That is my git username and I have used it for other patches/purposes, but I might update in the future with the full name.
"Might"? OK, so this is not a known identity case, then please use full
name *now*. For all entries. Don't post your usernames to mailing list.
Best regards,
Krzysztof
prev parent reply other threads:[~2024-05-31 7:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 12:01 [PATCH] dt-bindings: iio: adc: add a7779 doc ranechita
2024-05-22 13:33 ` Krzysztof Kozlowski
2024-05-23 17:03 ` Jonathan Cameron
2024-05-29 15:25 ` Nechita, Ramona
2024-05-31 7:45 ` Krzysztof Kozlowski [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=ef601549-47a2-49cd-9c9c-1ea35ac7c1ee@kernel.org \
--to=krzk@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=Ramona.Nechita@analog.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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.