linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Vipin K Parashar <vipin@linux.vnet.ibm.com>
To: Linux ppc dev <linuxppc-dev@lists.ozlabs.org>
Cc: Andrea Gelmini <andrea.gelmini@gelma.net>,
	Stewart Smith <stewart@linux.vnet.ibm.com>
Subject: Re: [PATCH 0215/1529] Fix typo
Date: Wed, 25 May 2016 00:40:44 +0530	[thread overview]
Message-ID: <5744A734.2040505@linux.vnet.ibm.com> (raw)
In-Reply-To: <20160521120413.11129-1-andrea.gelmini@gelma.net>


On Saturday 21 May 2016 05:34 PM, Andrea Gelmini wrote:
> Signed-off-by: Andrea Gelmini <andrea.gelmini@gelma.net>

Reviewed-by: Vipin K Parashar <vipin@linux.vnet.ibm.com>

> ---
>   arch/powerpc/include/asm/opal-api.h | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/powerpc/include/asm/opal-api.h b/arch/powerpc/include/asm/opal-api.h
> index 9bb8ddf..70b5cbc 100644
> --- a/arch/powerpc/include/asm/opal-api.h
> +++ b/arch/powerpc/include/asm/opal-api.h
> @@ -802,7 +802,7 @@ struct opal_sg_entry {
>   };
>
>   /*
> - * Candiate image SG list.
> + * Candidate image SG list.
>    *
>    * length = VER | length
>    */
> @@ -852,7 +852,7 @@ struct opal_i2c_request {
>    * with individual elements being 16 bits wide to fetch the system
>    * wide EPOW status. Each element in the buffer will contain the
>    * EPOW status in it's bit representation for a particular EPOW sub
> - * class as defiend here. So multiple detailed EPOW status bits
> + * class as defined here. So multiple detailed EPOW status bits
>    * specific for any sub class can be represented in a single buffer
>    * element as it's bit representation.
>    */

      reply	other threads:[~2016-05-24 19:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-21 12:04 [PATCH 0215/1529] Fix typo Andrea Gelmini
2016-05-24 19:10 ` Vipin K Parashar [this message]

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=5744A734.2040505@linux.vnet.ibm.com \
    --to=vipin@linux.vnet.ibm.com \
    --cc=andrea.gelmini@gelma.net \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=stewart@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).