All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: 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: Tue, 23 Nov 2021 21:09:36 +0200	[thread overview]
Message-ID: <YZ08cAbJ7MYuPq8h@smile.fi.intel.com> (raw)
In-Reply-To: <767f36e9-e043-06dd-f847-7405524b432e@infradead.org>

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@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.
> > 
> > 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@infradead.org>

Thanks!
Wolfram, can it be applied now or should I resend?

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2021-11-23 19:09 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
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 [this message]
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=YZ08cAbJ7MYuPq8h@smile.fi.intel.com \
    --to=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 \
    --cc=rdunlap@infradead.org \
    /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.