Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: andrea.gelmini@gelma.net (Andrea Gelmini)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0085/1529] Fix typo
Date: Sat, 21 May 2016 12:21:57 +0000	[thread overview]
Message-ID: <20160521122157.GA6289@li61-168.members.linode.com> (raw)
In-Reply-To: <20160521115556.GV19428@n2100.arm.linux.org.uk>

On Sat, May 21, 2016 at 12:55:56PM +0100, Russell King - ARM Linux wrote:
> On Sat, May 21, 2016 at 01:47:59PM +0200, Andrea Gelmini wrote:
> > Signed-off-by: Andrea Gelmini <andrea.gelmini@gelma.net>
> > ---
> >  arch/arm/include/asm/ucontext.h | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/arch/arm/include/asm/ucontext.h b/arch/arm/include/asm/ucontext.h
> > index 14749ae..b4d2d0f 100644
> > --- a/arch/arm/include/asm/ucontext.h
> > +++ b/arch/arm/include/asm/ucontext.h
> > @@ -8,7 +8,7 @@
> >   * ucontext now has room for all registers which need to be saved and
> >   * restored.  Coprocessor registers are stored in uc_regspace.  Each
> >   * coprocessor's saved state should start with a documented 32-bit magic
> > - * number, followed by a 32-bit word giving the coproccesor's saved size.
> > + * number, followed by a 32-bit word giving the coprocessor saved size.
> 
> The original is fine, and I'd say is more correct.

My point was about the spelling: coproccesor (double C, single S).

I don't resend a new version of the patch.
My interest is notify it, don't care to have commit in kernel for such
little thing.
I guess is easier if you fix it with next batch of your patches.

Bye,
Andrea

  reply	other threads:[~2016-05-21 12:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-21 11:47 [PATCH 0085/1529] Fix typo Andrea Gelmini
2016-05-21 11:55 ` Russell King - ARM Linux
2016-05-21 12:21   ` Andrea Gelmini [this message]
2016-05-21 12:49     ` Russell King - ARM Linux

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=20160521122157.GA6289@li61-168.members.linode.com \
    --to=andrea.gelmini@gelma.net \
    --cc=linux-arm-kernel@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox