From: Conor Dooley <conor@kernel.org>
To: Sean Anderson <seanga2@gmail.com>
Cc: Yanhong Wang <yanhong.wang@starfivetech.com>,
u-boot@lists.denx.de, Rick Chen <rick@andestech.com>,
Leo <ycliang@andestech.com>, Lukasz Majewski <lukma@denx.de>,
Lee Kuan Lim <kuanlim.lee@starfivetech.com>,
Jianlong Huang <jianlong.huang@starfivetech.com>,
Emil Renner Berthing <kernel@esmil.dk>
Subject: Re: [PATCH v2 00/17] Basic StarFive JH7110 RISC-V SoC support
Date: Sat, 21 Jan 2023 22:05:47 +0000 [thread overview]
Message-ID: <Y8xhuxsDsAWhlBpf@spud> (raw)
In-Reply-To: <6363344f-1448-ddf6-9459-94a1b44e27d3@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 643 bytes --]
> > Apologies if I have missed it somewhere - but where is patch 12?
> > I don't see it on lore.kernel.org nor in my inbox :(
> https://lore.kernel.org/all/20230118082907.31629-1-yanhong.wang@starfivetech.com/
Oh, thanks! Hopefully I can provide a tested-by so...
> Not sure why it isn't with the rest of the series.
Ehh, well it seems to be missing an In-Reply-To header, so perhaps it
was missing from the directory or w/e they ran send-email from & only
sent at a later date.
FWIW Yanhong, git send-email allows you to set that header so that
things do get threaded properly. AFAIU it's --in-reply-to=<msg-id>
Happy New Year,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-01-21 22:06 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 8:11 [PATCH v2 00/17] Basic StarFive JH7110 RISC-V SoC support Yanhong Wang
2023-01-18 8:11 ` [PATCH v2 01/17] riscv: cpu: jh7110: Add support for jh7110 SoC Yanhong Wang
2023-01-18 8:11 ` [PATCH v2 02/17] cache: starfive: Add StarFive JH7110 support Yanhong Wang
2023-01-18 8:11 ` [PATCH v2 03/17] dt-bindings: reset: Add StarFive JH7110 reset definitions Yanhong Wang
2023-01-18 8:11 ` [PATCH v2 04/17] reset: starfive: jh7110: Add reset driver for StarFive JH7110 SoC Yanhong Wang
2023-01-18 8:11 ` [PATCH v2 05/17] dt-bindings: clock: Add StarFive JH7110 clock definitions Yanhong Wang
2023-01-21 18:37 ` Sean Anderson
2023-01-18 8:11 ` [PATCH v2 06/17] clk: starfive: Add StarFive JH7110 clock driver Yanhong Wang
2023-01-21 18:56 ` Sean Anderson
2023-02-16 3:16 ` yanhong wang
2023-01-18 8:11 ` [PATCH v2 07/17] dt-bindings: pinctrl: Add StarFive JH7110 pinctrl definitions Yanhong Wang
2023-01-18 8:11 ` [PATCH v2 08/17] pinctrl: starfive: Add StarFive JH7110 driver Yanhong Wang
2023-01-18 8:11 ` [PATCH v2 09/17] ram: starfive: add ddr driver Yanhong Wang
2023-01-18 8:11 ` [PATCH v2 10/17] board: starfive: add StarFive VisionFive v2 board support Yanhong Wang
2023-01-21 17:38 ` Sean Anderson
2023-01-18 8:11 ` [PATCH v2 11/17] riscv: cpu: jh7110: Add Kconfig for StarFive JH7110 SoC Yanhong Wang
2023-01-18 8:11 ` [PATCH v2 13/17] board: starfive: Add TARGET_STARFIVE_VISIONFIVE2 to Kconfig Yanhong Wang
2023-01-18 8:11 ` [PATCH v2 14/17] riscv: dts: jh7110: Add initial StarFive JH7110 device tree Yanhong Wang
2023-01-19 6:18 ` David Abdurachmanov
2023-01-19 6:26 ` Sean Anderson
2023-01-19 18:30 ` Conor Dooley
2023-01-19 19:16 ` Sean Anderson
2023-01-19 19:25 ` Conor Dooley
2023-01-20 1:37 ` Sean Anderson
2023-02-16 5:50 ` yanhong wang
2023-01-18 8:11 ` [PATCH v2 15/17] riscv: dts: jh7110: Add initial u-boot " Yanhong Wang
2023-01-18 8:11 ` [PATCH v2 16/17] riscv: dts: jh7110: Add initial StarFive VisionFive v2 board " Yanhong Wang
2023-01-21 18:46 ` Sean Anderson
2023-02-16 6:20 ` yanhong wang
2023-01-18 8:11 ` [PATCH v2 17/17] configs: starfive: add starfive_visionfive2_defconfig Yanhong Wang
2023-01-23 14:53 ` Andreas Schwab
2023-02-16 7:28 ` yanhong wang
2023-02-16 14:17 ` Heinrich Schuchardt
2023-01-21 21:36 ` [PATCH v2 00/17] Basic StarFive JH7110 RISC-V SoC support Conor Dooley
2023-01-21 21:56 ` Sean Anderson
2023-01-21 22:05 ` Conor Dooley [this message]
2023-01-22 18:42 ` Conor Dooley
2023-02-10 17:41 ` Conor Dooley
2023-02-16 7:39 ` yanhong wang
2023-01-24 0:28 ` Heinrich Schuchardt
2023-02-16 9:01 ` yanhong wang
2023-01-24 14:46 ` Andreas Schwab
2023-02-06 7:38 ` Jan Kiszka
2023-02-07 15:46 ` Bin Meng
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=Y8xhuxsDsAWhlBpf@spud \
--to=conor@kernel.org \
--cc=jianlong.huang@starfivetech.com \
--cc=kernel@esmil.dk \
--cc=kuanlim.lee@starfivetech.com \
--cc=lukma@denx.de \
--cc=rick@andestech.com \
--cc=seanga2@gmail.com \
--cc=u-boot@lists.denx.de \
--cc=yanhong.wang@starfivetech.com \
--cc=ycliang@andestech.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