From: Randy Dunlap <rdunlap@infradead.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-i2c <linux-i2c@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [PATCH v1 1/1] i2c: designware: Fix the kernel doc description for struct dw_i2c_dev
Date: Fri, 12 Nov 2021 08:43:16 -0800 [thread overview]
Message-ID: <07932f56-ec2d-46a5-7c8e-3f4aab7afd35@infradead.org> (raw)
In-Reply-To: <CAHp75Vd71WPosA8Sy999Mb5ZiGEGg-y3vxYsYz3st5Ng2PJ98A@mail.gmail.com>
On 11/12/21 8:26 AM, Andy Shevchenko wrote:
> On Fri, Nov 12, 2021 at 6:01 PM Randy Dunlap <rdunlap@infradead.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.
thanks.
--
~Randy
next prev parent reply other threads:[~2021-11-12 16:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 12:34 [PATCH v1 1/1] i2c: designware: Fix the kernel doc description for struct dw_i2c_dev Andy Shevchenko
2021-11-12 13:39 ` Jarkko Nikula
2021-11-12 16:01 ` Randy Dunlap
2021-11-12 16:26 ` Andy Shevchenko
2021-11-12 16:43 ` Randy Dunlap [this message]
2021-11-15 14:18 ` Andy Shevchenko
2021-11-15 15:26 ` Wolfram Sang
2021-11-15 15:46 ` Randy Dunlap
2021-11-23 19:09 ` Andy Shevchenko
2021-11-29 9:43 ` Wolfram Sang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=07932f56-ec2d-46a5-7c8e-3f4aab7afd35@infradead.org \
--to=rdunlap@infradead.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.