lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <058aeecd-d9cb-43c4-8cd8-b1e8012b6448@axiado.com>
Date: Tue, 24 Jun 2025 23:54:30 +0000
From: Harshit Shah <hshah@...ado.com>
To: Krzysztof Kozlowski <krzk@...nel.org>, Rob Herring <robh@...nel.org>,
	Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>,
	Linus Walleij <linus.walleij@...aro.org>, Bartosz Golaszewski
	<brgl@...ev.pl>, Arnd Bergmann <arnd@...db.de>, Catalin Marinas
	<catalin.marinas@....com>, Will Deacon <will@...nel.org>, Jan Kotas
	<jank@...ence.com>
CC: "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org"
	<linux-arm-kernel@...ts.infradead.org>, "linux-gpio@...r.kernel.org"
	<linux-gpio@...r.kernel.org>, "soc@...ts.linux.dev" <soc@...ts.linux.dev>
Subject: Re: [PATCH v3 3/7] dt-bindings: gpio: gpio-cdns: convert to YAML

On 6/23/2025 11:34 PM, Krzysztof Kozlowski wrote:
> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
>
> On 23/06/2025 19:28, Harshit Shah wrote:
>> +
>> +  ngpios:
>> +    minimum: 1
>> +    maximum: 32
>> +    description: Number of GPIO lines supported, maximum 32.
> Don't repeat constraints in free form text.
>
> No need to resend just for that.

Got it. I will remove the "description".

> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
> <form letter>
> This is an automated instruction, just in case, because many review tags
> are being ignored. If you know the process, just skip it entirely
> (please do not feel offended by me posting it here - no bad intentions
> intended, no patronizing, I just want to avoid wasted efforts). If you
> do not know the process, here is a short explanation:
>
> Please add Acked-by/Reviewed-by/Tested-by tags when posting new versions
> of patchset, under or above your Signed-off-by tag, unless patch changed
> significantly (e.g. new properties added to the DT bindings). Tag is
> "received", when provided in a message replied to you on the mailing
> list. Tools like b4 can help here ('b4 trailers -u ...'). However,
> there's no need to repost patches *only* to add the tags. The upstream
> maintainer will do that for tags received on the version they apply.
>
> Full context and explanation:
> https://elixir.bootlin.com/linux/v6.15/source/Documentation/process/submitting-patches.rst#L591
> </form letter>

I was not aware of this before, apologies for the same. I will add this 
line of this from next patchset as per your suggestion.

I will take care for all the patches in this series. Thank you Krzysztof.

Regards,

Harshit.


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ