From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: linuxppc-dev@lists.ozlabs.org, gregkh@linuxfoundation.org,
Bhaskar Chowdhury <unixbhaskar@gmail.com>,
arnd@arndb.de, fbarrat@linux.ibm.com,
linux-kernel@vger.kernel.org, ajd@linux.ibm.com
Cc: rdunlap@infradead.org
Subject: Re: [PATCH] cxl: Fix couple of spellings
Date: Wed, 31 Mar 2021 12:09:40 +1100 [thread overview]
Message-ID: <161715298060.226945.13634069948401550126.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20210322023307.168754-1-unixbhaskar@gmail.com>
On Mon, 22 Mar 2021 08:03:07 +0530, Bhaskar Chowdhury wrote:
> s/filesytem/filesystem/
> s/symantics/semantics/
Applied to powerpc/next.
[1/1] cxl: Fix couple of spellings
https://git.kernel.org/powerpc/c/e23ecdf9fd87c547a3ac55bcebaf7df28df2fab0
cheers
prev parent reply other threads:[~2021-03-31 1:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 2:33 [PATCH] cxl: Fix couple of spellings Bhaskar Chowdhury
2021-03-22 3:02 ` Randy Dunlap
2021-03-22 15:24 ` Andrew Donnellan
2021-03-31 1:09 ` 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=161715298060.226945.13634069948401550126.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=ajd@linux.ibm.com \
--cc=arnd@arndb.de \
--cc=fbarrat@linux.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=rdunlap@infradead.org \
--cc=unixbhaskar@gmail.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).