From: Eric Chan <ericchancf@google.com>
To: parri.andrea@gmail.com
Cc: aou@eecs.berkeley.edu, conor.dooley@microchip.com,
ericchancf@google.com, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, palmer@dabbelt.com,
paul.walmsley@sifive.com
Subject: Re: [PATCH v2] riscv/fence: Consolidate fence definitions and define __{mb,rmb,wmb}
Date: Tue, 13 Feb 2024 14:57:53 +0000 [thread overview]
Message-ID: <20240213145753.2423739-1-ericchancf@google.com> (raw)
In-Reply-To: <ZctGwaTnEfkum50a@andrea>
Hi Andrea,
Thank you for reviewing my patch! I appreciate the feedback.
Referring to your suggestions, the final result is as follows:
1/4 - riscv/barrier: Define __{mb,rmb,wmb}
2/4 - riscv/barrier: Define RISCV_FULL_BARRIER
3/4 - riscv/barrier: Consolidate fence definitions
4/4 - riscv/barrier: Resolve checkpath.pl error
I've updated patch v3[https://marc.info/?l=linux-kernel&m=170783431129245]
Please let me know if you have any further questions or suggestions.
Sincerely,
Eric Chan
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Eric Chan <ericchancf@google.com>
To: parri.andrea@gmail.com
Cc: aou@eecs.berkeley.edu, conor.dooley@microchip.com,
ericchancf@google.com, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, palmer@dabbelt.com,
paul.walmsley@sifive.com
Subject: Re: [PATCH v2] riscv/fence: Consolidate fence definitions and define __{mb,rmb,wmb}
Date: Tue, 13 Feb 2024 14:57:53 +0000 [thread overview]
Message-ID: <20240213145753.2423739-1-ericchancf@google.com> (raw)
In-Reply-To: <ZctGwaTnEfkum50a@andrea>
Hi Andrea,
Thank you for reviewing my patch! I appreciate the feedback.
Referring to your suggestions, the final result is as follows:
1/4 - riscv/barrier: Define __{mb,rmb,wmb}
2/4 - riscv/barrier: Define RISCV_FULL_BARRIER
3/4 - riscv/barrier: Consolidate fence definitions
4/4 - riscv/barrier: Resolve checkpath.pl error
I've updated patch v3[https://marc.info/?l=linux-kernel&m=170783431129245]
Please let me know if you have any further questions or suggestions.
Sincerely,
Eric Chan
next prev parent reply other threads:[~2024-02-13 14:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 12:50 [PATCH] riscv/fence: Consolidate fence definitions and define __{mb,rmb,wmb} Eric Chan
2024-02-09 12:50 ` Eric Chan
2024-02-12 8:03 ` Conor Dooley
2024-02-12 8:03 ` Conor Dooley
2024-02-12 10:59 ` [PATCH v2] " Eric Chan
2024-02-12 10:59 ` Eric Chan
2024-02-13 10:38 ` Andrea Parri
2024-02-13 10:38 ` Andrea Parri
2024-02-13 14:57 ` Eric Chan [this message]
2024-02-13 14:57 ` Eric Chan
2024-02-13 15:03 ` [PATCH] " Eric Chan
2024-02-13 15:03 ` Eric Chan
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=20240213145753.2423739-1-ericchancf@google.com \
--to=ericchancf@google.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=parri.andrea@gmail.com \
--cc=paul.walmsley@sifive.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 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.