From: Conor Dooley <conor@kernel.org>
To: Qinglin Pan <panqinglin2020@iscas.ac.cn>
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
linux-riscv@lists.infradead.org, jeff@riscv.org,
xuyinan@ict.ac.cn, ajones@ventanamicro.com
Subject: Re: [PATCH v11 0/3] riscv, mm: detect svnapot cpu support at runtime
Date: Thu, 16 Feb 2023 22:04:23 +0000 [thread overview]
Message-ID: <Y+6oZ4mu1/jcfDIg@spud> (raw)
In-Reply-To: <0711567e-39a4-09a4-aefa-4c5a55e196c9@iscas.ac.cn>
[-- Attachment #1.1: Type: text/plain, Size: 1261 bytes --]
On Wed, Feb 15, 2023 at 10:47:49AM +0800, Qinglin Pan wrote:
> On 2/15/23 8:02 AM, Palmer Dabbelt wrote:
> > On Thu, 15 Dec 2022 22:21:06 PST (-0800), panqinglin2020@iscas.ac.cn wrote:
> > This is triggering some build failures. I sent along a fix before
> > realizing they're actually coming from this patch set:
> > https://lore.kernel.org/all/20230214201358.10647-1-palmer@rivosinc.com/
> > . If it's OK I'll just squash that in here, so I can avoid a broken
> > build.
>
> There is a newer v13(in [1]) based on new ISA extension API. But it still
> have conchuod/build_rv64_gcc_allmodconfig check failed in it[2].
> I have no idea whether it is caused by my patchset since the output seems
> not related to my code.. Please let me know if there is anything I
> need to modify.
Yah, looking at that it is actually just noise. For some reason the
before-the-patch build the scatterlist warnings got merged with other
warnings.
If you look at the "raw" version of the gist it's pretty easy to see:
https://gist.githubusercontent.com/conor-pwbot/0a1850594abdf3aebe4b3026a52a682d/raw/a5ed91502e27795c57c573824a66aff7f68f4323/stderr
I dunno what caused that, I'll have to take a look.
You can consider that one to be noise, sorry!
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2023-02-16 22:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 6:21 [PATCH v11 0/3] riscv, mm: detect svnapot cpu support at runtime panqinglin2020
2022-12-16 6:21 ` [PATCH v11 1/3] riscv: mm: modify pte format for Svnapot panqinglin2020
2022-12-19 21:51 ` Conor Dooley
2022-12-26 16:01 ` Andrew Jones
2022-12-26 18:40 ` Conor Dooley
2022-12-26 19:19 ` Andrew Jones
2023-01-08 6:21 ` Qinglin Pan
2022-12-16 6:21 ` [PATCH v11 2/3] riscv: mm: support Svnapot in hugetlb page panqinglin2020
2022-12-16 6:21 ` [PATCH v11 3/3] riscv: mm: support Svnapot in huge vmap panqinglin2020
2022-12-19 21:48 ` [PATCH v11 0/3] riscv, mm: detect svnapot cpu support at runtime Conor Dooley
2023-01-14 4:54 ` Qinglin Pan
2023-02-01 11:58 ` Qinglin Pan
2023-02-15 0:02 ` Palmer Dabbelt
2023-02-15 2:47 ` Qinglin Pan
2023-02-16 22:04 ` Conor Dooley [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=Y+6oZ4mu1/jcfDIg@spud \
--to=conor@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=jeff@riscv.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=panqinglin2020@iscas.ac.cn \
--cc=xuyinan@ict.ac.cn \
/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