linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: Fixing a cputhread code documentation
Date: Thu, 17 May 2012 11:00:00 +0530	[thread overview]
Message-ID: <4FB48CD8.30709@linux.vnet.ibm.com> (raw)
In-Reply-To: <4FB12570.9090503@linux.vnet.ibm.com>

Hey Ben,

Because its too minor a documentation fix, did not write any description.
Not sure how it works, I thought this would be clubbed with other incoming
documentation fix in the same area. 

On Monday 14 May 2012 09:02 PM, Anshuman Khandual wrote:

> diff --git a/arch/powerpc/include/asm/cputhreads.h b/arch/powerpc/include/asm/cputhreads.h
> index ce516e5..ac3eedb 100644
> --- a/arch/powerpc/include/asm/cputhreads.h
> +++ b/arch/powerpc/include/asm/cputhreads.h
> @@ -9,7 +9,7 @@
>   * Note: This implementation is limited to a power of 2 number of
>   * threads per core and the same number for each core in the system
>   * (though it would work if some processors had less threads as long
> - * as the CPU numbers are still allocated, just not brought offline).
> + * as the CPU numbers are still allocated, just not brought online).
>   *
>   * However, the API allows for a different implementation in the future
>   * if needed, as long as you only use the functions and not the variables
> 
> --
> Anshuman Khandual

      reply	other threads:[~2012-05-17  5:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-14 15:32 Fixing a cputhread code documentation Anshuman Khandual
2012-05-17  5:30 ` Anshuman Khandual [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=4FB48CD8.30709@linux.vnet.ibm.com \
    --to=khandual@linux.vnet.ibm.com \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).