From: <Conor.Dooley@microchip.com>
To: <panqinglin2020@iscas.ac.cn>, <conor@kernel.org>
Cc: <palmer@dabbelt.com>, <linux-riscv@lists.infradead.org>,
<jeff@riscv.org>, <xuyinan@ict.ac.cn>, <ajones@ventanamicro.com>,
<alex@ghiti.fr>, <jszhang@kernel.org>
Subject: Re: [PATCH v9 1/3] riscv: mm: modify pte format for Svnapot
Date: Thu, 8 Dec 2022 04:59:07 +0000 [thread overview]
Message-ID: <534c6246-2f7a-f919-932f-2d31dc277573@microchip.com> (raw)
In-Reply-To: <ae8753cd-038c-ecaa-3a39-72cf1340d764@iscas.ac.cn>
On 08/12/2022 04:51, Qinglin Pan wrote:
> On 2022/12/8 02:46, Conor Dooley wrote:
>> On Sun, Dec 04, 2022 at 10:11:35PM +0800, panqinglin2020@iscas.ac.cn wrote:
>>> From: Qinglin Pan <panqinglin2020@iscas.ac.cn>
>>> +#define for_each_napot_order(order) \
>>> + for (order = NAPOT_CONT_ORDER_BASE; order < NAPOT_ORDER_MAX; order++)
>>> +#define for_each_napot_order_rev(order) \
>>
>> Would it be terrible to do s/rev/reverse to make things more obvious?
>
> Maybe we should just keep it in the same style as existing macros like
> for_each_mem_range/for_each_mem_range_rev :)
Yah, makes sense. Sorry for the noise then!
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2022-12-08 4:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 14:11 [PATCH v9 0/3] riscv, mm: detect svnapot cpu support at runtime panqinglin2020
2022-12-04 14:11 ` [PATCH v9 1/3] riscv: mm: modify pte format for Svnapot panqinglin2020
2022-12-06 19:56 ` Conor Dooley
2022-12-07 18:46 ` Conor Dooley
2022-12-08 4:51 ` Qinglin Pan
2022-12-08 4:59 ` Conor.Dooley [this message]
2022-12-08 17:34 ` Qinglin Pan
2022-12-09 7:42 ` Andrew Jones
2022-12-09 14:33 ` Conor Dooley
2022-12-09 15:36 ` Qinglin Pan
2022-12-09 17:04 ` Andrew Jones
2022-12-08 14:55 ` Andrew Jones
2022-12-04 14:11 ` [PATCH v9 2/3] riscv: mm: support Svnapot in hugetlb page panqinglin2020
2022-12-07 18:55 ` Conor Dooley
2022-12-08 4:54 ` Qinglin Pan
2022-12-08 15:17 ` Andrew Jones
2022-12-08 17:43 ` Qinglin Pan
2022-12-04 14:11 ` [PATCH v9 3/3] riscv: mm: support Svnapot in huge vmap panqinglin2020
2022-12-07 18:59 ` Conor Dooley
2022-12-08 4:57 ` Qinglin Pan
2022-12-08 15:22 ` Andrew Jones
2022-12-08 17:39 ` Qinglin Pan
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=534c6246-2f7a-f919-932f-2d31dc277573@microchip.com \
--to=conor.dooley@microchip.com \
--cc=ajones@ventanamicro.com \
--cc=alex@ghiti.fr \
--cc=conor@kernel.org \
--cc=jeff@riscv.org \
--cc=jszhang@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.