Re: [PATCH v10 2/7] mfd: Add driver for ASUS Transformer embedded controller

--6dqlofrf2szwmrad
Content-Type: text/plain; protected-headers=v1; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PATCH v10 2/7] mfd: Add driver for ASUS Transformer embedded
 controller
MIME-Version: 1.0

On Sat, Jul 25, 2026 at 04:23:13PM +0300, Svyatoslav Ryhel wrote:
> =D1=87=D1=82, 23 =D0=BB=D0=B8=D0=BF. 2026=E2=80=AF=D1=80. =D0=BE 09:25 Uw=
e Kleine-K=C3=B6nig
> <[email protected]> =D0=BF=D0=B8=D1=88=D0=B5:
> >
> > Hello,
> >
> > On Tue, Jul 21, 2026 at 12:52:28PM +0300, Svyatoslav Ryhel wrote:
> > > From: Micha=C5=82 Miros=C5=82aw <[email protected]>
> > >
> > > Support Nuvoton NPCE795-based ECs as used in Asus Transformer TF201,
> > > TF300T, TF300TG, TF300TL and TF700T pad and dock, as well as TF101 do=
ck
> > > and TF600T, P1801-T and TF701T pad. This is a glue driver handling
> > > detection and common operations for EC's functions.
> > >
> > > Co-developed-by: Svyatoslav Ryhel <[email protected]>
> > > Signed-off-by: Svyatoslav Ryhel <[email protected]>
> > > Signed-off-by: Micha=C5=82 Miros=C5=82aw <[email protected]>
> >
> > Documentation/process/submitting-patches.rst has:
> >
> >         [...] the ordering of Signed-off-by: tags should reflect the
> >         chronological history of the patch insofar as possible [...]
> >
> > So your S-o-b should be last when you submit a patch.
> >
> > > +#include <linux/i2c.h>
> > > [...]
> > > +#include <linux/mod_devicetable.h>
> >
> > <linux/mod_devicetable.h> will go away soon. Please rely on
> > <linux/i2c.h> to provide a definition of struct of_device_id and drop
> > the #include of mod_devicetable.h.
> >
> > > +static const struct of_device_id asus_ec_match[] =3D {
> > > +     {
> > > +             .compatible =3D "asus,sl101-ec-dock",
> > > +             .data =3D &asus_ec_sl101_dock_data
> > > +     }, {
> > > +             .compatible =3D "asus,tf101-ec-dock",
> > > +             .data =3D &asus_ec_tf101_dock_data
> > > +     }, {
> > > +             .compatible =3D "asus,tf201-ec-pad",
> > > +             .data =3D &asus_ec_tf201_pad_data
> > > +     }, {
> > > +             .compatible =3D "asus,tf600t-ec-pad",
> > > +             .data =3D &asus_ec_tf600t_pad_data
> > > +     },
> > > +     { /* sentinel */ }
> > > +};
> >
> > Trailing comma after the assignments to .data please.
> >
>=20
> Sure, but out of curiosity, why in this case you ask for trailing
> comma and if entries are in one line, you don't.

Because this is the most used style. The rationale for the trailing
comma is that if you want to add a new assignment to a multiline
initializer you have to touch the line without comma:

 	}, {
 		.compatible =3D "asus,tf600t-ec-pad",
-		.data =3D &asus_ec_tf600t_pad_data
+		.data =3D &asus_ec_tf600t_pad_data,
+		.something_else =3D &foobar,
 	},

so if the comma is already there, the patch reduces to:

 	}, {
 		.compatible =3D "asus,tf600t-ec-pad",
 		.data =3D &asus_ec_tf600t_pad_data,
+		.something_else =3D &foobar,
 	},

=2E For adding a new assignment to:

 	{ .compatible =3D "..." }

you have to touch the line anyhow, so there is no advantage to already
have the comma. And then it seems parsimony prevails.

Best regards
Uwe

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

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

iQEzBAABCgAdFiEEP4GsaTp6HlmJrf7Tj4D7WH0S/k4FAmpp8zUACgkQj4D7WH0S
/k6ZNAf8DhR7uBfXuQZzNcJ2dR9KB5Mucc4l5ZRolBWJcq6FHN8KK2BbDb+bkrcE
pUhYeNPt0LnZBA6JHWhJAM1zlHnLaQ2PlBWxeR4EIwAhM8nyXcfHgmgMJxBHSeEQ
qHWXZKtQd90uCGYg4BnQO8LmgAQR610/ujayOjnD0EgB2Wy19ZkENuG5Nu+Irzef
8DWW0WMWbrTCP49l4fgVWsLE8/yOaBE1jBeyaZ17yXLwz5vbs6OfeCkqaK11AOnH
KXbRlcea/K7YZX7wPKZLhHMSvmzSk+NEQgQpg7+qgg7NYMLDgJFCfvFTWhNj5lqb
GcHcRJv6c3GBFhS3t9oSrHiBeXrX0A==
=JxD4
-----END PGP SIGNATURE-----

--6dqlofrf2szwmrad--