From: "Heiko Stübner" <heiko@sntech.de>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Alexey Charkov <alchark@gmail.com>,
linux-sound@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: ASoC: rockchip: Add compatible for RK3588 SPDIF
Date: Mon, 10 Feb 2025 15:04:22 +0100 [thread overview]
Message-ID: <870305083.0ifERbkFSE@diego> (raw)
In-Reply-To: <56d128d7-c4bd-48de-b823-0b88147220e1@sirena.org.uk>
Hi Mark,
Am Montag, 10. Februar 2025, 14:20:58 MEZ schrieb Mark Brown:
> 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.
With it being 3 weeks since the patch was originally posted, I thought
it might be the time to ask if the binding-patch was still around.
I vaguely do remember you saying in the past that if a patch hasn't
been applied/handled after X time-units, it wouldn't be in your inbox
anymore, but am not sure anymore ;-) .
WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Alexey Charkov <alchark@gmail.com>,
linux-sound@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: ASoC: rockchip: Add compatible for RK3588 SPDIF
Date: Mon, 10 Feb 2025 15:04:22 +0100 [thread overview]
Message-ID: <870305083.0ifERbkFSE@diego> (raw)
In-Reply-To: <56d128d7-c4bd-48de-b823-0b88147220e1@sirena.org.uk>
Hi Mark,
Am Montag, 10. Februar 2025, 14:20:58 MEZ schrieb Mark Brown:
> 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.
With it being 3 weeks since the patch was originally posted, I thought
it might be the time to ask if the binding-patch was still around.
I vaguely do remember you saying in the past that if a patch hasn't
been applied/handled after X time-units, it wouldn't be in your inbox
anymore, but am not sure anymore ;-) .
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-02-10 14:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 9:01 [PATCH 0/3] arm64: dts: rockchip: Add SPDIF on RK3588 Alexey Charkov
2025-01-20 9:01 ` Alexey Charkov
2025-01-20 9:01 ` [PATCH 1/3] dt-bindings: ASoC: rockchip: Add compatible for RK3588 SPDIF Alexey Charkov
2025-01-20 9:01 ` Alexey Charkov
2025-01-21 17:37 ` Conor Dooley
2025-01-21 17:37 ` Conor Dooley
2025-02-09 21:10 ` Heiko Stübner
2025-02-09 21:10 ` Heiko Stübner
2025-02-10 13:20 ` Mark Brown
2025-02-10 13:20 ` Mark Brown
2025-02-10 14:04 ` Heiko Stübner [this message]
2025-02-10 14:04 ` Heiko Stübner
2025-02-10 14:28 ` Mark Brown
2025-02-10 14:28 ` Mark Brown
2025-01-20 9:01 ` [PATCH 2/3] arm64: dts: rockchip: Add SPDIF nodes to RK3588(s) device trees Alexey Charkov
2025-01-20 9:01 ` Alexey Charkov
2025-01-20 9:01 ` [PATCH 3/3] arm64: dts: rockchip: Enable SPDIF output on H96 Max V58 Alexey Charkov
2025-01-20 9:01 ` Alexey Charkov
2025-02-10 18:06 ` (subset) [PATCH 0/3] arm64: dts: rockchip: Add SPDIF on RK3588 Mark Brown
2025-02-10 18:06 ` Mark Brown
2025-02-11 9:28 ` Heiko Stuebner
2025-02-11 9:28 ` Heiko Stuebner
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=870305083.0ifERbkFSE@diego \
--to=heiko@sntech.de \
--cc=alchark@gmail.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-sound@vger.kernel.org \
--cc=robh@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.