From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org
Subject: Re: [PATCH 0/6] mips: delete duplicated words
Date: Sun, 26 Jul 2020 10:22:14 +0200 [thread overview]
Message-ID: <20200726082214.GA5032@alpha.franken.de> (raw)
In-Reply-To: <20200726003429.20356-1-rdunlap@infradead.org>
On Sat, Jul 25, 2020 at 05:34:23PM -0700, Randy Dunlap wrote:
> Delete duplicated words in arch/mips/ header files.
>
> Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
> Cc: linux-mips@vger.kernel.org
>
> arch/mips/include/asm/io.h | 2 +-
> arch/mips/include/asm/octeon/cvmx-l2c.h | 2 +-
> arch/mips/include/asm/octeon/cvmx-pip.h | 2 +-
> arch/mips/include/asm/octeon/cvmx-pko.h | 7 +++----
> arch/mips/include/asm/octeon/cvmx-pow.h | 8 ++++----
> arch/mips/include/asm/octeon/octeon.h | 2 +-
> 6 files changed, 11 insertions(+), 12 deletions(-)
series applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2020-07-26 8:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-26 0:34 [PATCH 0/6] mips: delete duplicated words Randy Dunlap
2020-07-26 0:34 ` [PATCH 1/6] mips: io.h: delete duplicated word Randy Dunlap
2020-07-26 0:34 ` [PATCH 2/6] mips: octeon: cvmx-l2c.h: " Randy Dunlap
2020-07-26 0:34 ` [PATCH 3/6] mips: octeon: cvmx-pip.h: " Randy Dunlap
2020-07-26 0:34 ` [PATCH 4/6] mips: octeon: cvmx-pkoh: fix duplicated words Randy Dunlap
2020-07-26 0:34 ` [PATCH 5/6] mips: octeon: cvmx-pow.h: " Randy Dunlap
2020-07-26 0:34 ` [PATCH 6/6] mips: octeon: octeon.h: delete duplicated word Randy Dunlap
2020-07-26 8:22 ` Thomas Bogendoerfer [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=20200726082214.GA5032@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=rdunlap@infradead.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