linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: linux-doc@vger.kernel.org
Cc: linuxppc-dev@lists.ozlabs.org, Jeremy Kerr <jk@ozlabs.org>,
	Arnd Bergmann <arnd@arndb.de>, Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH] >>>>>>>>>>>>>>>>>>>>>>>>> BLURB <<<<<<<<<<<<<<<<<<<
Date: Mon, 29 Aug 2022 16:28:06 -0700	[thread overview]
Message-ID: <65f56cde-3df5-d912-82c6-fbac9eceffbf@infradead.org> (raw)
In-Reply-To: <20220829232653.25060-1-rdunlap@infradead.org>

Oops.
I'll correct the Subject and resend.


On 8/29/22 16:26, Randy Dunlap wrote:
> Fix a typo of "or" which should be "of".
> 
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Jeremy Kerr <jk@ozlabs.org>
> Cc: Arnd Bergmann <arnd@arndb.de>
> Cc: linuxppc-dev@lists.ozlabs.org
> Cc: Jonathan Corbet <corbet@lwn.net>
> ---
>  Documentation/filesystems/spufs/spufs.rst |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> --- a/Documentation/filesystems/spufs/spufs.rst
> +++ b/Documentation/filesystems/spufs/spufs.rst
> @@ -227,7 +227,7 @@ Files
>                from the data buffer, updating the value of the specified signal
>                notification register.  The signal  notification  register  will
>                either be replaced with the input data or will be updated to the
> -              bitwise OR or the old value and the input data, depending on the
> +              bitwise OR of the old value and the input data, depending on the
>                contents  of  the  signal1_type,  or  signal2_type respectively,
>                file.
>  

-- 
~Randy

      reply	other threads:[~2022-08-29 23:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-29 23:26 [PATCH] >>>>>>>>>>>>>>>>>>>>>>>>> BLURB <<<<<<<<<<<<<<<<<<< Randy Dunlap
2022-08-29 23:28 ` Randy Dunlap [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=65f56cde-3df5-d912-82c6-fbac9eceffbf@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=arnd@arndb.de \
    --cc=corbet@lwn.net \
    --cc=jk@ozlabs.org \
    --cc=linux-doc@vger.kernel.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).