Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Mon, 7 Aug 2023 07:36:03 +0700
From:   Bagas Sanjaya <bagasdotme@gmail.com>
To:     Christophe Leroy <christophe.leroy@csgroup.eu>,
        "zhangyongle001@208suo.com" <zhangyongle001@208suo.com>,
        "mpe@ellerman.id.au" <mpe@ellerman.id.au>,
        "npiggin@gmail.com" <npiggin@gmail.com>
Cc:     "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] floppy: ERROR: that open brace { should be on the
 previous line
Message-ID: <ZNA8c4HlbbJ4XE30@debian.me>
References: <058c3448e220ee16bcb5e588271b685c@208suo.com>
 <72a156e7-d15d-629e-9166-461622ad0f21@csgroup.eu>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="SErABh50vbaitwzM"
Content-Disposition: inline
In-Reply-To: <72a156e7-d15d-629e-9166-461622ad0f21@csgroup.eu>
Precedence: bulk


--SErABh50vbaitwzM
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Aug 04, 2023 at 04:05:09PM +0000, Christophe Leroy wrote:
> Hello,
>=20
> Le 20/07/2023 =C3=A0 12:17, zhangyongle001@208suo.com a =C3=A9crit=C2=A0:
> > [Vous ne recevez pas souvent de courriers de zhangyongle001@208suo.com.=
=20
> > D?couvrez pourquoi ceci est important ?=20
> > https://aka.ms/LearnAboutSenderIdentification ]
> >=20
> > Fix twoce occurrences of the checkpatch.pl error:
> > ERROR: that open brace { should be on the previous line
>=20
>=20
> Can you please explain the purpose of those changes ? Do you use some=20
> tools that get disturbed by such cosmetic errors ? Otherwise what is=20
> your reason ?

Hi,

208suo.com people do checkpatch fixes (that is, they run
scripts/checkpatch.pl -f <random source file> then try to make the script
happy). Steven warned them to not submitting such patches again [1] but
they keep spamming maintainers with checkpatch patches (ignoring the review
warning). I voiced this concern when reviewing one of their patches and
Jani replied that such one-way interaction with kernel communty is
detrimental [2].

The exact same situation happened last year involving developers from
cdjrlc.com domain. They also did trivial patches, including mostly
(and notoriously known for) redundant word stripping. While some of these
patches were accepted, others were not with reviews requesting changes in
v2, yet they also ignored reviews. In fact, in the early waves of 208suo.com
patches, they used the same email infra as 208suo.com people and they sent
patches as HTML emails (which were rejected by mailing lists obviously)
so that the latter people have to send their patches on their behalf
(but corrupted since 208suo.com people used Roundcube instead of
git-send-email(1)).

Regarding 208suo.com's mail infra, after I pointed out this [3], they
changed the infra so that patches sent didn't get corrupted. Thus, they did
listen in regard of tooling and infra changes, but they deliberately
doesn't answer code reviews.

Thanks.

[1]: https://lore.kernel.org/lkml/20230720134501.01f9f1de@gandalf.local.hom=
e/
[2]: https://lore.kernel.org/lkml/87cz07vvwu.fsf@intel.com/
[3]: https://lore.kernel.org/lkml/ZJK7sC4i+MK98k%2F+@debian.me/

>=20
> We don't accept such standelone minor cosmetic changes at the first=20
> place because it looks like a waste of time.

PS: And in fact, complicating stable backports...

--=20
An old man doll... just what I always wanted! - Clara

--SErABh50vbaitwzM
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEABYKAB0WIQSSYQ6Cy7oyFNCHrUH2uYlJVVFOowUCZNA8aQAKCRD2uYlJVVFO
o1acAQDW60nBwSLxR3hsP5HX++ukVRwWzC4LuylPdMo2w/GNcAEA9uw09JR+PKcp
Jg6+XPElt+x2FfUaAd0pHuRAiVBaKgc=
=J/zU
-----END PGP SIGNATURE-----

--SErABh50vbaitwzM--