From: Walker Chen <walker.chen@starfivetech.com>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Claudiu Beznea <Claudiu.Beznea@microchip.com>,
Jaroslav Kysela <perex@perex.cz>, "Takashi Iwai" <tiwai@suse.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor.dooley@microchip.com>,
Emil Renner Berthing <emil.renner.berthing@canonical.com>,
<alsa-devel@alsa-project.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-riscv@lists.infradead.org>
Subject: Re: [PATCH v4 2/3] ASoC: starfive: Add JH7110 TDM driver
Date: Mon, 15 May 2023 20:47:33 +0800 [thread overview]
Message-ID: <d6dad1e0-59f7-e78c-cb9b-28342fbf0fac@starfivetech.com> (raw)
In-Reply-To: <ZGIOmWyxPGOuWHx+@finisterre.sirena.org.uk>
On 2023/5/15 18:51, Mark Brown wrote:
> On Mon, May 15, 2023 at 04:29:07PM +0800, Walker Chen wrote:
>
>> I have submitted new version of patch for TDM driver. Could you please help to review and give your comments?
>
> Please don't send content free pings and please allow a reasonable time
> for review. People get busy, go on holiday, attend conferences and so
> on so unless there is some reason for urgency (like critical bug fixes)
> please allow at least a couple of weeks for review. If there have been
> review comments then people may be waiting for those to be addressed.
>
> Sending content free pings adds to the mail volume (if they are seen at
> all) which is often the problem and since they can't be reviewed
> directly if something has gone wrong you'll have to resend the patches
> anyway, so sending again is generally a better approach though there are
> some other maintainers who like them - if in doubt look at how patches
> for the subsystem are normally handled.
Hi Mark,
Sorry for that! Please forgive me for asking so eagerly.
I will pay attention to this in the future.
Best regards,
Walker
next prev parent reply other threads:[~2023-05-15 12:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 9:15 [PATCH v4 0/3] Add TDM audio on StarFive JH7110 Walker Chen
2023-05-11 9:15 ` [PATCH v4 1/3] ASoC: dt-bindings: Add TDM controller bindings for " Walker Chen
2023-05-11 9:15 ` [PATCH v4 2/3] ASoC: starfive: Add JH7110 TDM driver Walker Chen
2023-05-15 8:29 ` Walker Chen
2023-05-15 10:51 ` Mark Brown
2023-05-15 12:47 ` Walker Chen [this message]
2023-05-17 8:35 ` Claudiu.Beznea
2023-05-24 8:20 ` Walker Chen
2023-05-11 9:15 ` [PATCH v4 3/3] riscv: dts: starfive: add the node and pins configuration for tdm Walker Chen
2023-05-15 8:44 ` Walker Chen
2023-05-15 8:58 ` Conor Dooley
2023-05-15 11:20 ` Mark Brown
2023-05-15 12:36 ` Walker 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=d6dad1e0-59f7-e78c-cb9b-28342fbf0fac@starfivetech.com \
--to=walker.chen@starfivetech.com \
--cc=Claudiu.Beznea@microchip.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=emil.renner.berthing@canonical.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=perex@perex.cz \
--cc=robh+dt@kernel.org \
--cc=tiwai@suse.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).