From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Sergio Pérez" <sergio@pereznus.es>, linux-iio@vger.kernel.org
Cc: tduszyns@gmail.com, jic23@kernel.org, lars@metafoo.de,
robh@kernel.org, conor+dt@kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] iio: light: bh1750: Add hardware reset support via GPIO
Date: Thu, 20 Mar 2025 08:15:25 +0100 [thread overview]
Message-ID: <e43c534b-a1ef-46e9-a5cf-39f328ba895a@kernel.org> (raw)
In-Reply-To: <22b70f84-0918-43e7-92f5-c8bdb4a68363@pereznus.es>
On 18/03/2025 20:51, Sergio Pérez wrote:
>> Please read the guides carefully. The process is extremely simple as:
>>
>> git add ...
>> git commit --signed-off
>> git format-patch -v3 -2
>> scripts/chekpatch.pl v3*
>> scripts/get_maintainers.pl --no-git-fallback v3*
>> git send-email *
>> (or just use my git_send_email for last two)
>> (or just use b4 for last four)
>>
>> The burden of reading the contributing guides is on you. We documented
>> all this on purpose, so we will not have to repeat this on every email.
> Thank you very much, I have followed the instructions with total
> precision and carefully read all the documentation. I have submitted
> both patches as v4 version.
> Apologies for the inconvenience.
No, you did not send proper v4. If you followed the process the v4 would
be properly threaded, but it was not.
What commands EXACTLY did you use?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-20 7:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250316145514.627-1-sergio@pereznus.es>
[not found] ` <01f48f6d-55a4-4dbe-b1ae-ef8c54dcc1ff@kernel.org>
[not found] ` <64182937-29e9-45dc-aa2f-5f2b739056a1@me.com>
2025-03-18 13:28 ` [PATCH] iio: light: bh1750: Add hardware reset support via GPIO Krzysztof Kozlowski
2025-03-18 14:16 ` Sergio Pérez
2025-03-18 15:16 ` Krzysztof Kozlowski
2025-03-18 16:06 ` Sergio Pérez
2025-03-18 16:21 ` Krzysztof Kozlowski
2025-03-18 16:23 ` Krzysztof Kozlowski
2025-03-18 17:26 ` Sergio Pérez
2025-03-18 17:37 ` Krzysztof Kozlowski
2025-03-18 19:51 ` Sergio Pérez
2025-03-20 7:15 ` Krzysztof Kozlowski [this message]
2025-03-19 8:46 ` Krzysztof Kozlowski
2025-03-19 16:26 ` Sergio Pérez
2025-03-20 7:18 ` Krzysztof Kozlowski
[not found] ` <20250317115815.2416c741@jic23-huawei>
2025-03-18 14:35 ` Sergio Pérez
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=e43c534b-a1ef-46e9-a5cf-39f328ba895a@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sergio@pereznus.es \
--cc=tduszyns@gmail.com \
/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