public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
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: Wed, 19 Mar 2025 09:46:52 +0100	[thread overview]
Message-ID: <0507608a-91fd-4206-b921-942677c5f8d3@kernel.org> (raw)
In-Reply-To: <ac008fb8-7c82-4b9c-9d24-52ea38b920e5@kernel.org>

On 18/03/2025 18:37, Krzysztof Kozlowski wrote:
>>
>> I've now run the tool correctly on my patch file and have fixed the 
>> identified issues:
>> - Removed trailing whitespace
>> - Fixed lines exceeding 79 characters
>> - Fixed the inconsistency between the description and example for 
>> reset-gpios
>> - Modified the existing example instead of adding a new one
>> - Ensured proper line endings and formatting
>> - Used proper get_maintainers.pl to include all recipients
>>
> 
> 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 *

Please read this again. I gave you detailed instruction which you still
decided not to follow. The instructions are quite precise on purpose,
because other method leads to wrong patchset - broken that or other way.


> (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.
> 
> 
> [1]
> https://github.com/search?q=repo%3Akrzk%2Ftools%20git_send_email&type=code
> 
> Best regards,
> Krzysztof


Best regards,
Krzysztof

  parent reply	other threads:[~2025-03-19  8:46 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
2025-03-19  8:46                 ` Krzysztof Kozlowski [this message]
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=0507608a-91fd-4206-b921-942677c5f8d3@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