[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56d128d7-c4bd-48de-b823-0b88147220e1@sirena.org.uk>
Date: Mon, 10 Feb 2025 13:20:58 +0000
From: Mark Brown <broonie@...nel.org>
To: Heiko Stübner <heiko@...ech.de>
Cc: Liam Girdwood <lgirdwood@...il.com>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Alexey Charkov <alchark@...il.com>, linux-sound@...r.kernel.org,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: ASoC: rockchip: Add compatible for
RK3588 SPDIF
On Sun, Feb 09, 2025 at 10:10:47PM +0100, Heiko Stübner wrote:
> Am Montag, 20. Januar 2025, 10:01:27 MEZ schrieb Alexey Charkov:
> > Add a compatible string for SPDIF on RK3588, which is similar to the
> > one on RK3568.
> as the binding is more in the driver-realm, is this patch still
> somewhere on your radar?
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.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists