From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: Huang Pei <huangpei@loongson.cn>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
<ambrosehua@gmail.com>
Cc: Bibo Mao <maobibo@loongson.cn>,
Andrew Morton <akpm@linux-foundation.org>,
<linux-mips@vger.kernel.org>, <linux-arch@vger.kernel.org>,
<linux-mm@kvack.org>, Jiaxun Yang <jiaxun.yang@flygoat.com>,
Paul Burton <paulburton@kernel.org>,
Li Xuefeng <lixuefeng@loongson.cn>,
Yang Tiezhu <yangtiezhu@loongson.cn>,
Gao Juxin <gaojuxin@loongson.cn>,
Fuxin Zhang <zhangfx@lemote.com>,
Huacai Chen <chenhuacai@loongson.cn>
Subject: Re: [PATCH 6/6] MIPS: loongson64: fix FTLB configuration
Date: Tue, 23 Nov 2021 14:55:19 +0300 [thread overview]
Message-ID: <f40206d8-2563-f1aa-8494-715406463bbe@omp.ru> (raw)
In-Reply-To: <20211123074927.12461-7-huangpei@loongson.cn>
Hello!
On 23.11.2021 10:49, Huang Pei wrote:
> Commit "da1bd29742b1" makes 'set_ftlb_enable' called under
You should cite the commit the same way as in the Fixes: tag (except you
can break up the long lines).
> c->cputype unset, which leaves FTLB disabled on BOTH 3A2000
> and 3A3000
>
> Fixes: da1bd29742b1 ("MIPS: Loongson64: Probe CPU features via CPUCFG")
> Signed-off-by: Huang Pei <huangpei@loongson.cn>
[...]
MBR, Sergey
next prev parent reply other threads:[~2021-11-23 11:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 7:49 [PATCH V2]: bugfix Huang Pei
2021-11-23 7:49 ` [PATCH 1/6] hamradio: fix macro redefine warning Huang Pei
2021-11-23 7:49 ` [PATCH 2/6] slip: " Huang Pei
2021-11-23 7:49 ` [PATCH 3/6] MIPS: rework local_t operation on MIPS64 Huang Pei
2021-11-23 7:49 ` [PATCH 4/6] MIPS: tx39: fix tx39_flush_cache_page Huang Pei
2021-11-23 7:49 ` [PATCH 5/6] MIPS: use 3-level pgtable for 64KB page size on MIPS_VA_BITS_48 Huang Pei
2021-11-23 7:49 ` [PATCH 6/6] MIPS: loongson64: fix FTLB configuration Huang Pei
2021-11-23 11:55 ` Sergey Shtylyov [this message]
2021-11-23 8:56 ` [PATCH V2]: bugfix Thomas Bogendoerfer
2021-11-24 3:31 ` Huang Pei
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=f40206d8-2563-f1aa-8494-715406463bbe@omp.ru \
--to=s.shtylyov@omp.ru \
--cc=akpm@linux-foundation.org \
--cc=ambrosehua@gmail.com \
--cc=chenhuacai@loongson.cn \
--cc=gaojuxin@loongson.cn \
--cc=huangpei@loongson.cn \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lixuefeng@loongson.cn \
--cc=maobibo@loongson.cn \
--cc=paulburton@kernel.org \
--cc=tsbogend@alpha.franken.de \
--cc=yangtiezhu@loongson.cn \
--cc=zhangfx@lemote.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