From: "Jiaxun Yang" <jiaxun.yang@flygoat.com>
To: "Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
FreeFlyingSheep <chris.chenfeiyang@gmail.com>
Cc: "Thomas Gleixner" <tglx@linutronix.de>,
peterz@infradead.org, luto@kernel.org,
"Arnd Bergmann" <arnd@arndb.de>,
"Feiyang Chen" <chenfeiyang@loongson.cn>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
linux-arch@vger.kernel.org, "Huacai Chen" <chenhuacai@kernel.org>,
"Zhou Yanjie" <zhouyu@wanyeetech.com>,
"H. Nikolaus Schaller" <hns@goldelico.com>
Subject: Re: [PATCH v2 0/2] MIPS: convert to generic entry
Date: Fri, 24 Sep 2021 00:51:35 +0100 [thread overview]
Message-ID: <16d09c59-ba76-4dca-b9f2-bde502b96ecf@www.fastmail.com> (raw)
In-Reply-To: <20210921155708.GA12237@alpha.franken.de>
在2021年9月21日九月 下午4:57，Thomas Bogendoerfer写道：
>
> can people, who provided performance numbers for v1 do the same for v2 ?
Sorry I just move abroad (to UK) to seek higher education. Currently I don't have any MIPS device available so I won't be able to provide test results as v1.
I'll try to get some MIPS devices soonish.
Thanks.
>
> Thomas,
>
> --
> Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
> good idea. [ RFC1925, 2.3 ]
--
- Jiaxun
prev parent reply other threads:[~2021-09-23 23:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 1:50 [PATCH v2 0/2] MIPS: convert to generic entry Feiyang Chen
2021-09-14 1:50 ` [PATCH v2 1/2] MIPS: convert syscall " Feiyang Chen
2021-09-14 1:50 ` [PATCH v2 2/2] MIPS: convert irq " Feiyang Chen
2021-09-14 8:54 ` [PATCH v2 0/2] MIPS: convert " Jiaxun Yang
2021-09-14 9:30 ` Feiyang Chen
2021-09-21 15:57 ` Thomas Bogendoerfer
2021-09-23 14:33 ` Zhou Yanjie
2021-10-13 15:00 ` Zhou Yanjie
2021-10-18 19:32 ` Maciej W. Rozycki
2021-10-19 2:22 ` Feiyang Chen
2021-10-19 8:33 ` Maciej W. Rozycki
2021-10-22 2:19 ` Feiyang Chen
2021-09-23 23:51 ` Jiaxun Yang [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=16d09c59-ba76-4dca-b9f2-bde502b96ecf@www.fastmail.com \
--to=jiaxun.yang@flygoat.com \
--cc=arnd@arndb.de \
--cc=chenfeiyang@loongson.cn \
--cc=chenhuacai@kernel.org \
--cc=chris.chenfeiyang@gmail.com \
--cc=hns@goldelico.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tsbogend@alpha.franken.de \
--cc=zhouyu@wanyeetech.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).