All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Mark Brown <broonie@kernel.org>, Laszlo Papp <lpapp@kde.org>
Cc: linux-doc@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] include/linux/regmap.h: fix a couple of typos
Date: Wed, 08 Jan 2014 14:04:19 -0800	[thread overview]
Message-ID: <52CDCB63.3030705@infradead.org> (raw)
In-Reply-To: <20140108190758.GY31886@sirena.org.uk>

On 01/08/14 11:07, Mark Brown wrote:
> On Wed, Jan 08, 2014 at 06:59:57PM +0000, Laszlo Papp wrote:
>> On Wed, Jan 8, 2014 at 6:07 PM, Mark Brown <broonie@kernel.org> wrote:
>>> On Wed, Jan 08, 2014 at 05:22:18PM +0000, Laszlo Papp wrote:
> 
>>>> - *             (eg, a clear on read interrupt status register). If this
>>>> + *             (e.g. a clear on read interrupt status register). If this
> 
>>> This is somewhat outdated orthorgraphy...
> 
>> Pardon ?
> 
> It's not that common to write it as an abbreviation (even though it is
> one) and for some random reason you've decided to drop the comma which
> is standard.

Good catch.  I somehow overlooked that change (dropped comma) in the patch.

e.g.,

-- 
~Randy

  parent reply	other threads:[~2014-01-08 22:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-08 17:22 [PATCH] include/linux/regmap.h: fix a couple of typos Laszlo Papp
2014-01-08 18:07 ` Mark Brown
2014-01-08 18:59   ` Laszlo Papp
2014-01-08 19:07     ` Mark Brown
2014-01-08 21:02       ` Laszlo Papp
2014-01-08 21:08         ` Laszlo Papp
2014-01-08 21:49           ` Mark Brown
2014-01-09  1:46             ` Laszlo Papp
2014-01-09  2:43               ` Randy Dunlap
2014-01-09 10:22                 ` Laszlo Papp
2014-01-09 12:23                   ` Mark Brown
2014-01-09 11:18                 ` Mark Brown
2014-01-08 22:04       ` Randy Dunlap [this message]
2014-01-08 19:07   ` Randy Dunlap

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=52CDCB63.3030705@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=broonie@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lpapp@kde.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.