From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: "open list:BROADCOM NVRAM DRIVER" <linux-mips@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"Maciej W . Rozycki" <macro@orcam.me.uk>,
Ralf Baechle <ralf@linux-mips.org>,
George Cherian <gcherian@marvell.com>,
Huacai Chen <chenhuacai@kernel.org>,
Jiaxun Yang <jiaxun.yang@flygoat.com>
Subject: Re: [PATCH v2] MIPS: select CPU_MIPS64 for remaining MIPS64 CPUs
Date: Wed, 3 Mar 2021 00:03:38 +0100 [thread overview]
Message-ID: <20210302230338.GB3808@alpha.franken.de> (raw)
In-Reply-To: <CAHmME9qw4VSgjAugYdms7j32A0TU_2C2EFMufsjc1LfYnczZEA@mail.gmail.com>
On Mon, Mar 01, 2021 at 05:27:46PM +0100, Jason A. Donenfeld wrote:
> Hey Thomas,
>
> Would you mind sending this for 5.12 in an rc at some point, rather
> than waiting for 5.13? I'd like to see this backported to 5.10 and 5.4
> for OpenWRT.
why is this so important for OpenWRT ? Just to select CRYPTO_POLY1305_MIPS ?
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2021-03-03 0:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-27 12:26 [PATCH] MIPS: select CPU_MIPS64 for remaining MIPS64 CPUs Jason A. Donenfeld
2021-02-27 13:40 ` Maciej W. Rozycki
2021-02-27 22:59 ` Jason A. Donenfeld
2021-02-27 23:02 ` [PATCH v2] " Jason A. Donenfeld
2021-03-01 14:49 ` Thomas Bogendoerfer
2021-03-01 16:27 ` Jason A. Donenfeld
2021-03-02 23:03 ` Thomas Bogendoerfer [this message]
2021-03-03 0:05 ` Jason A. Donenfeld
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=20210302230338.GB3808@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=Jason@zx2c4.com \
--cc=chenhuacai@kernel.org \
--cc=gcherian@marvell.com \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=ralf@linux-mips.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