From: Conor Dooley <conor@kernel.org>
To: Yangyu Chen <cyy@cyyself.name>
Cc: ajones@ventanamicro.com, aou@eecs.berkeley.edu, i@zenithal.me,
krzysztof.kozlowski+dt@linaro.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, palmer@dabbelt.com,
paul.walmsley@sifive.com, robh+dt@kernel.org, soha@lohu.info,
twd2.me@gmail.com
Subject: Re: [PATCH v2 0/2] riscv: allow case-insensitive ISA string parsing
Date: Fri, 28 Apr 2023 19:37:53 +0100 [thread overview]
Message-ID: <20230428-flagship-algorithm-9f10e99a184f@spud> (raw)
In-Reply-To: <tencent_D5671CCB7149630242B61A1BF8B80581B409@qq.com>
[-- Attachment #1.1: Type: text/plain, Size: 668 bytes --]
On Sat, Apr 29, 2023 at 12:26:00AM +0800, Yangyu Chen wrote:
> Sorry for the cover letter being detached with patches. My mailing
> service provider will override the Message-IDs which caused this
> trouble. I will send the cover letter first to get the correct Message-ID
> before sending the rest of the patches the next time.
At least it doesn't overwrite the in-reply-to headers also, so the
patches are at least threaded.
> The cover letter is at https://lore.kernel.org/linux-riscv/tencent_8492B68063042E768C758871A3171FBD2006@qq.com/
> The patches is at https://lore.kernel.org/linux-riscv/tencent_85F69423082E524C478844E31D5F8920A506@qq.com/
>
[-- 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
WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor@kernel.org>
To: Yangyu Chen <cyy@cyyself.name>
Cc: ajones@ventanamicro.com, aou@eecs.berkeley.edu, i@zenithal.me,
krzysztof.kozlowski+dt@linaro.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, palmer@dabbelt.com,
paul.walmsley@sifive.com, robh+dt@kernel.org, soha@lohu.info,
twd2.me@gmail.com
Subject: Re: [PATCH v2 0/2] riscv: allow case-insensitive ISA string parsing
Date: Fri, 28 Apr 2023 19:37:53 +0100 [thread overview]
Message-ID: <20230428-flagship-algorithm-9f10e99a184f@spud> (raw)
In-Reply-To: <tencent_D5671CCB7149630242B61A1BF8B80581B409@qq.com>
[-- Attachment #1: Type: text/plain, Size: 668 bytes --]
On Sat, Apr 29, 2023 at 12:26:00AM +0800, Yangyu Chen wrote:
> Sorry for the cover letter being detached with patches. My mailing
> service provider will override the Message-IDs which caused this
> trouble. I will send the cover letter first to get the correct Message-ID
> before sending the rest of the patches the next time.
At least it doesn't overwrite the in-reply-to headers also, so the
patches are at least threaded.
> The cover letter is at https://lore.kernel.org/linux-riscv/tencent_8492B68063042E768C758871A3171FBD2006@qq.com/
> The patches is at https://lore.kernel.org/linux-riscv/tencent_85F69423082E524C478844E31D5F8920A506@qq.com/
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-04-28 18:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230428141601.678489-1-cyy@cyyself.name>
2023-04-28 14:16 ` [PATCH v2 1/2] riscv: allow case-insensitive ISA string parsing Yangyu Chen
2023-04-28 14:16 ` Yangyu Chen
2023-04-28 16:26 ` [PATCH v2 0/2] " Yangyu Chen
2023-04-28 16:26 ` Yangyu Chen
2023-04-28 18:37 ` Conor Dooley [this message]
2023-04-28 18:37 ` Conor Dooley
2023-04-28 19:27 ` [PATCH v2 1/2] " Conor Dooley
2023-04-28 19:27 ` Conor Dooley
2023-04-29 10:10 ` Andrew Jones
2023-04-29 10:10 ` Andrew Jones
2023-05-01 11:51 ` Conor Dooley
2023-05-01 11:51 ` Conor Dooley
2023-04-28 14:16 ` [PATCH v2 2/2] dt-bindings: riscv: drop invalid comment about riscv,isa lower-case reasoning Yangyu Chen
2023-04-28 14:16 ` Yangyu Chen
2023-04-28 17:05 ` Conor Dooley
2023-04-28 17:05 ` Conor Dooley
2023-04-28 14:15 [PATCH v2 0/2] riscv: allow case-insensitive ISA string parsing Yangyu Chen
2023-04-28 14:15 ` Yangyu Chen
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=20230428-flagship-algorithm-9f10e99a184f@spud \
--to=conor@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=aou@eecs.berkeley.edu \
--cc=cyy@cyyself.name \
--cc=i@zenithal.me \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=soha@lohu.info \
--cc=twd2.me@gmail.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.