linux-kernel - Re: [PATCH 1/3] MAINTAINERS: iio: migrate invensense email address to tdk domain

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:
 <FR3P281MB17576E4FFFDB3B61677BB1C8CE712@FR3P281MB1757.DEUP281.PROD.OUTLOOK.COM>
Date: Thu, 3 Oct 2024 12:49:56 +0000
From: Jean-Baptiste Maneyrol <Jean-Baptiste.Maneyrol@....com>
To: Krzysztof Kozlowski <krzk@...nel.org>,
        Jonathan Cameron
	<jic23@...nel.org>,
        Lars-Peter Clausen <lars@...afoo.de>, Rob Herring
	<robh@...nel.org>,
        Krzysztof Kozlowski <krzk+dt@...nel.org>,
        Conor Dooley
	<conor+dt@...nel.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-iio@...r.kernel.org" <linux-iio@...r.kernel.org>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: Re: [PATCH 1/3] MAINTAINERS: iio: migrate invensense email address to
 tdk domain

Hello,

I apologize first for doing a top response, but I'm stuck with an email tool that doesn't allows me to have better response than that. And sadly, I don't think there is something I can do about it.

In fact, when trying checkpatch --strict I don't have any warning on my side. I was using in fact checkpatch -f which is for testing source file and not patch. I tried upgrading git to latest version, I don't see any change. b4 is version 0.14.2.


./scripts/checkpatch.pl --strict test/*.patch
--------------------------------------------------------------------
test/0001-MAINTAINERS-iio-migrate-invensense-email-address-to-.patch
--------------------------------------------------------------------
total: 0 errors, 0 warnings, 0 checks, 8 lines checked

test/0001-MAINTAINERS-iio-migrate-invensense-email-address-to-.patch has no obvious style problems and is ready for submission.
--------------------------------------------------------------------
test/0002-dt-bindings-iio-imu-migrate-InvenSense-email-to-TDK-.patch
--------------------------------------------------------------------
total: 0 errors, 0 warnings, 0 checks, 16 lines checked

test/0002-dt-bindings-iio-imu-migrate-InvenSense-email-to-TDK-.patch has no obvious style problems and is ready for submission.
--------------------------------------------------------------------
test/0003-MAINTAINERS-iio-imu-add-entry-for-InvenSense-MPU-605.patch
--------------------------------------------------------------------
total: 0 errors, 0 warnings, 0 checks, 14 lines checked

test/0003-MAINTAINERS-iio-imu-add-entry-for-InvenSense-MPU-605.patch has no obvious style problems and is ready for submission.


What are the errors you are seeing on your side for these patches?

Thanks,
JB

________________________________________
From: Krzysztof Kozlowski <krzk@...nel.org>
Sent: Thursday, October 3, 2024 09:45
To: Jean-Baptiste Maneyrol <Jean-Baptiste.Maneyrol@....com>; Jonathan Cameron <jic23@...nel.org>; Lars-Peter Clausen <lars@...afoo.de>; Rob Herring <robh@...nel.org>; Krzysztof Kozlowski <krzk+dt@...nel.org>; Conor Dooley <conor+dt@...nel.org>
Cc: linux-kernel@...r.kernel.org <linux-kernel@...r.kernel.org>; linux-iio@...r.kernel.org <linux-iio@...r.kernel.org>; devicetree@...r.kernel.org <devicetree@...r.kernel.org>
Subject: Re: [PATCH 1/3] MAINTAINERS: iio: migrate invensense email address to tdk domain
 
This Message Is From an External Sender
This message came from outside your organization.
 
On 03/10/2024 09:37, Jean-Baptiste Maneyrol via B4 Relay wrote:
> From: Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@....com>
> 
> InvenSense is part of TDK group. Update email address to use the
> TDK domain.

Please run scripts/checkpatch.pl and fix reported warnings. Then please
run `scripts/checkpatch.pl --strict` and (probably) fix more warnings.
Some warnings can be ignored, especially from --strict run, but the code
here looks like it needs a fix. Feel free to get in touch if the warning
is not clear.

Best regards,
Krzysztof