[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YZ08cAbJ7MYuPq8h@smile.fi.intel.com>
Date: Tue, 23 Nov 2021 21:09:36 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Randy Dunlap <rdunlap@...radead.org>
Cc: linux-i2c <linux-i2c@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Jarkko Nikula <jarkko.nikula@...ux.intel.com>,
Mika Westerberg <mika.westerberg@...ux.intel.com>
Subject: Re: [PATCH v1 1/1] i2c: designware: Fix the kernel doc description
for struct dw_i2c_dev
On Mon, Nov 15, 2021 at 07:46:42AM -0800, Randy Dunlap wrote:
> On 11/12/21 8:43 AM, Randy Dunlap wrote:
> > On 11/12/21 8:26 AM, Andy Shevchenko wrote:
> > > On Fri, Nov 12, 2021 at 6:01 PM Randy Dunlap <rdunlap@...radead.org> wrote:
> > > > On 11/12/21 4:34 AM, Andy Shevchenko wrote:
> > >
> > > ...
> > >
> > > > > + * @rinfo: I²C GPIO recovery information
> > > >
> > > > Preferably: "I2C"
> > >
> > > Why?
> >
> > See below vvvvvvvvvvvvvvvvv:
> > > > like it is in thousands of places in the kernel source tree.
> >
> >
> > > UTF-8 has been established for more than a decade. I prefer to use the
> > > proper form of the abbreviation (*).
> > >
> > > *) Check UM10204.pdf.
>
>
> > > Yes, I am aware of what is in the spec.
> >
> > Wolfram, what do you prefer?
>
> > I prefer I2C. But it is more a reading habit. I would neither enforce
> > I2C nor I²C.
>
> OK, let's leave it as Andy sent it then.
>
> Acked-by: Randy Dunlap <rdunla@...radead.org>
Thanks!
Wolfram, can it be applied now or should I resend?
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists