From: Stephen Boyd <sboyd@kernel.org>
To: David Yang <mmyangfl@gmail.com>
Cc: David Yang <mmyangfl@gmail.com>,
Michael Turquette <mturquette@baylibre.com>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/6] Add CRG driver for Hi3798MV100 SoC
Date: Tue, 21 Mar 2023 16:04:59 -0700 [thread overview]
Message-ID: <2cafff47ba27fb712146019b6e283ab3.sboyd@kernel.org> (raw)
In-Reply-To: <20230321200031.1812026-1-mmyangfl@gmail.com>
Quoting David Yang (2023-03-21 13:00:21)
> This series adds CRG driver for Hi3798MV100 SoC.
>
> v2: move bindings to a separate patch
> v3: fix bindings commit message, reorganize patches
> v4: add ethernet and gpu clocks
> v5: add complex clock
> v6: migrate devm api
Some general comments. Typically we link to previous rounds with lore
links like
https://lore.kernel.org/r/message.id.of.previous.cover.letter
and also generate patches with `git format-patch --base` so we know what
baseline kernel version was used to develop on. And, please send your
emails To: something/somebody. Right now the To: header is empty, so it
looks like spam.
prev parent reply other threads:[~2023-03-21 23:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 20:00 [PATCH v6 0/6] Add CRG driver for Hi3798MV100 SoC David Yang
2023-03-21 20:00 ` [PATCH v6 1/6] clk: hisilicon: Rename Hi3798CV200 to Hi3798 David Yang
2023-03-21 20:00 ` [PATCH v6 2/6] clk: hisilicon: Extract common functions David Yang
2023-03-21 20:00 ` [PATCH v6 3/6] clk: hisilicon: Migrate devm APIs David Yang
2023-03-21 23:02 ` Stephen Boyd
2023-03-22 8:03 ` kernel test robot
2023-03-21 20:00 ` [PATCH v6 4/6] clk: hisilicon: Add complex clock for Hi3798 David Yang
2023-03-21 20:00 ` [PATCH v6 5/6] dt-bindings: clock: Add Hi3798MV100 CRG David Yang
2023-03-21 20:00 ` [PATCH v6 6/6] clk: hisilicon: Add CRG driver for Hi3798MV100 SoC David Yang
2023-03-21 23:04 ` Stephen Boyd [this message]
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=2cafff47ba27fb712146019b6e283ab3.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmyangfl@gmail.com \
--cc=mturquette@baylibre.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