From: Wenliang Yan <wenliang202407@163.com>
To: linux@roeck-us.net
Cc: conor+dt@kernel.org, corbet@lwn.net, devicetree@vger.kernel.org,
jdelvare@suse.com, krzk+dt@kernel.org, krzk@kernel.org,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
robh@kernel.org, wenliang202407@163.com
Subject: Re: [PATCH v3 1/2] dt-bindings:Add SQ52206 to ina2xx devicetree bindings
Date: Thu, 23 Jan 2025 15:58:02 +0800 [thread overview]
Message-ID: <20250123075802.1105859-1-wenliang202407@163.com> (raw)
In-Reply-To: <0eda52b5-59c2-4ad2-bb2c-5846dbfbf3e9@roeck-us.net>
At 2025-01-23 11:30:59, "Guenter Roeck" <linux@roeck-us.net> wrote:
>On 1/22/25 17:36, Wenliang Yan wrote:
>> At 2025-01-22 15:59:02, "Krzysztof Kozlowski" <krzk@kernel.org> wrote:
>>> On Wed, Jan 22, 2025 at 09:29:39AM +0800, Wenliang Yan wrote:
>>>> Add the sq52206 compatible to the ina2xx.yaml
>>>>
>>>> Signed-off-by: Wenliang Yan <wenliang202407@163.com>
>>>> ---
>>>>
>>>> Add the meaning of 'shunt-gain' in SQ52206.
>>>
>>> You already sent v3... and you got comment from me. You ignored both
>>> Conor and me, so me doing third time the same and expecting different
>>> results would be definition of insanity.
>>>
>>> Please read carefully submitting patches before posting new version.
>>>
>>> Best regards,
>>> Krzysztof
>>
>> Sorry, I have received your comment and 'acked'. I was originally
>> planning to resend [PATCH v3 2/2], because I have not received a
>> response from Guenter Roeck<linux@roeck-us.net>. However, I forgot to
>> add 'RESEND' in the title. Thank you for your patient reply.
>> I apologize again.
>>
>
>A resend after just four days, plus dropping all Acks ? Are you serious ?
>
>Please keep in mind that not all of us are getting paid for doing this.
>If I am otherwise busy, it will take longer. Sometimes it will take
>much longer. If you resend a patches, they will end up at the tail
>of my review queue. If you drop Acks, expect me to dig it all up,
>and figure out on my own what if anything changed, the patches will
>end up even further down, as in "I'll look into this series if I have
>nothing else left to review".
>
>Guenter
Sorry for the inconvenience caused by my actions. I am just concerned that
you did not receive the email, and I will continue to wait for your review
and correction.
Best regards,
Wenliang Yan
next prev parent reply other threads:[~2025-01-23 8:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250122012940.1005571-1-wenliang202407@163.com>
2025-01-22 1:29 ` [PATCH v3 1/2] dt-bindings:Add SQ52206 to ina2xx devicetree bindings Wenliang Yan
2025-01-22 7:59 ` Krzysztof Kozlowski
2025-01-23 1:36 ` Wenliang Yan
2025-01-23 3:30 ` Guenter Roeck
2025-01-23 7:58 ` Wenliang Yan [this message]
2025-01-23 8:47 ` Krzysztof Kozlowski
[not found] <20250117082017.688212-1-wenliang202407@163.com>
2025-01-17 8:20 ` Wenliang Yan
2025-01-18 14:37 ` Krzysztof Kozlowski
2025-01-24 7:43 ` Wenliang Yan
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=20250123075802.1105859-1-wenliang202407@163.com \
--to=wenliang202407@163.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox