From: Conor Dooley <conor@kernel.org>
To: Chen Wang <unicornxw@gmail.com>
Cc: aou@eecs.berkeley.edu, chao.wei@sophgo.com,
devicetree@vger.kernel.org, guoren@kernel.org,
jszhang@kernel.org, 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,
xiaoguang.xing@sophgo.com, apatel@ventanamicro.com,
Chen Wang <unicorn_wang@outlook.com>
Subject: Re: [PATCH v4 00/10] Add Milk-V Pioneer RISC-V board support
Date: Wed, 4 Oct 2023 16:24:03 +0100 [thread overview]
Message-ID: <20231004-rival-wow-1412dca8c490@spud> (raw)
In-Reply-To: <CAHAQgRChywKWKX2=Cyn4VBrZKfy6pY2meHtVqRyBcfRUm7mHYQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 252 bytes --]
On Wed, Oct 04, 2023 at 11:14:54PM +0800, Chen Wang wrote:
> Sorry, please ignore this email, it was sent out by mistake.
What are you doing that this has happened twice today?
Don't you just do `git send-email /path/to/directory/containing/patches`?
[-- 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
next prev parent reply other threads:[~2023-10-04 15:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 15:11 [PATCH v4 00/10] Add Milk-V Pioneer RISC-V board support Chen Wang
2023-10-04 14:20 ` [PATCH v4 01/10] riscv: Add SOPHGO SOC family Kconfig support Chen Wang
2023-10-04 14:27 ` Chen Wang
2023-10-04 15:14 ` [PATCH v4 00/10] Add Milk-V Pioneer RISC-V board support Chen Wang
2023-10-04 15:24 ` Conor Dooley [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-04 15:37 Chen Wang
2023-10-06 1:05 ` Chen Wang
2023-10-04 14:17 Chen Wang
2023-10-04 14:30 ` Chen Wang
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=20231004-rival-wow-1412dca8c490@spud \
--to=conor@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=apatel@ventanamicro.com \
--cc=chao.wei@sophgo.com \
--cc=devicetree@vger.kernel.org \
--cc=guoren@kernel.org \
--cc=jszhang@kernel.org \
--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=unicorn_wang@outlook.com \
--cc=unicornxw@gmail.com \
--cc=xiaoguang.xing@sophgo.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;
as well as URLs for NNTP newsgroup(s).