From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Paul Mackerras <paulus@samba.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: powerpc/fsl-rio: fix spelling mistake "reserverd" -> "reserved"
Date: Mon, 24 Dec 2018 00:27:51 +1100 (AEDT) [thread overview]
Message-ID: <43N3875xhrz9sDN@ozlabs.org> (raw)
In-Reply-To: <20181120151230.32159-1-alexandre.belloni@bootlin.com>
On Tue, 2018-11-20 at 15:12:30 UTC, Alexandre Belloni wrote:
> Fix a spelling mistake in a register description.
>
> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/a083787680f80f2c16316a1d907bf8
cheers
prev parent reply other threads:[~2018-12-23 13:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 15:12 [PATCH] powerpc/fsl-rio: fix spelling mistake "reserverd" -> "reserved" Alexandre Belloni
2018-12-23 13:27 ` Michael Ellerman [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=43N3875xhrz9sDN@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=alexandre.belloni@bootlin.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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).