From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: William Qiu <william.qiu@starfivetech.com>,
linux-riscv@lists.infradead.org, devicetree@vger.kernel.org
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Hal Feng <hal.feng@linux.starfivetech.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] StarFive's SDIO/eMMC driver support
Date: Tue, 27 Dec 2022 14:07:01 +0100 [thread overview]
Message-ID: <02e8c75f-658f-320c-7c90-64ccf2beccbe@linaro.org> (raw)
In-Reply-To: <20221227115856.460790-1-william.qiu@starfivetech.com>
On 27/12/2022 12:58, William Qiu wrote:
> Hi,
>
> This patchset adds initial rudimentary support for the StarFive
> designware mobile storage host controller driver. And this driver will
> be used in StarFive's VisionFive 2 board. The main purpose of adding
> this driver is to accommodate the ultra-high speed mode of eMMC.
>
> The last patch should be applied after the patchset [1]:
> [1] https://lore.kernel.org/all/20221118011714.70877-1-hal.feng@starfivetech.com/
It's a duplicate? Why do I have two of them in mailbox? Isn't this v3 then?
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-12-27 13:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-27 11:58 [PATCH v2 0/3] StarFive's SDIO/eMMC driver support William Qiu
2022-12-27 11:58 ` [PATCH v2 1/3] dt-bindings: mmc: Add bindings for StarFive William Qiu
2022-12-27 11:58 ` [PATCH v2 2/3] mmc: starfive: Add sdio/emmc driver support William Qiu
2022-12-27 11:58 ` [PATCH v2 3/3] riscv: dts: starfive: Add mmc node William Qiu
2022-12-27 13:07 ` Krzysztof Kozlowski [this message]
2022-12-28 10:46 ` [PATCH v2 0/3] StarFive's SDIO/eMMC driver support William Qiu
-- strict thread matches above, loose matches on Subject: below --
2022-12-27 12:22 William Qiu
2023-01-06 8:44 ` William Qiu
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=02e8c75f-658f-320c-7c90-64ccf2beccbe@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=aou@eecs.berkeley.edu \
--cc=devicetree@vger.kernel.org \
--cc=hal.feng@linux.starfivetech.com \
--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=william.qiu@starfivetech.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).