On Mon, Feb 10, 2025 at 03:04:22PM +0100, Heiko Stübner wrote: > Am Montag, 10. Februar 2025, 14:20:58 MEZ schrieb Mark Brown: > > 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 ;-) . A big part of what that form letter is saying is that it's better to chase by resending since that ensures that if things have been lost the actual thing that you're looking for action on is right here. If you just send a ping either it'll get buried along with the original patch or there won't be information to hand.
Attachment:
signature.asc
Description: PGP signature
- References:
- [PATCH 0/3] arm64: dts: rockchip: Add SPDIF on RK3588
- From: Alexey Charkov
- Re: [PATCH 1/3] dt-bindings: ASoC: rockchip: Add compatible for RK3588 SPDIF
- From: Heiko Stübner
- Re: [PATCH 1/3] dt-bindings: ASoC: rockchip: Add compatible for RK3588 SPDIF
- From: Mark Brown
- Re: [PATCH 1/3] dt-bindings: ASoC: rockchip: Add compatible for RK3588 SPDIF
- From: Heiko Stübner
- [PATCH 0/3] arm64: dts: rockchip: Add SPDIF on RK3588
- Prev by Date: Re: [PATCH v4 01/20] driver core: Split devres APIs to device/devres.h
- Next by Date: Re: [PATCH v4 01/20] driver core: Split devres APIs to device/devres.h
- Previous by thread: Re: [PATCH 1/3] dt-bindings: ASoC: rockchip: Add compatible for RK3588 SPDIF
- Next by thread: [PATCH 2/3] arm64: dts: rockchip: Add SPDIF nodes to RK3588(s) device trees
- Index(es):
![]() |