Re: [PATCH v1 0/2] ASoC: dt-bindings: qcom,sm8250: Add Hawi sound card

[Prasad Kumpatla]

On 7/14/2026 12:52 AM, Mark Brown wrote:
> On Mon, Jul 13, 2026 at 11:39:05PM +0530, Prasad Kumpatla wrote:
> > This series add support for sound card on Qualcomm Hawi boards.
> >
> > This series depends on:
> > 	- https://lore.kernel.org/all/20260712134110.3306763-1-prasad.kumpatla@xxxxxxxxxxxxxxxx/
> Which is a not directly legible link to "ASoC: qcom: add AudioReach TDM
> backend support" which itself has a dependency on some further in flight
> stuff also specified as a link to some random message ID with whatever
> pile of problems that has.
>
> This isn't directed at you specifically, this is a general problem which
> seems to be getting worse and worse with the Qualcomm patches.  There's
> multi-level stacks of dependencies, the dependencies are hard to follow
> and nothing seems to be moving at any great pace so I'm ending up with
> my review queue clogged with things which don't even apply due to the in
> flight stuff and it's hard to figure out what's going on.  Can you all
> please coordinate with each other and try to get whatever is at the
> bottom of these stacks of dependencies in?  If you have to send changes
> based on some in flight things specify those dependencies in so they're
> readable from the email.  Right now it just seems like there's a
> constant stream of stuff being thrown over the wall without any review
> going on.
>
> Please include human readable descriptions of things like commits and
> issues being discussed in e-mail in your mails, this makes them much
> easier for humans to read especially when they have no internet access.
> I do frequently catch up on my mail on flights or while otherwise
> travelling so this is even more pressing for me than just being about
> making things a bit easier to read.

Hi Mark,

Thank you for the feedback and for highlighting this broader issue.

That's a fair point. I'll update the cover letter to include concise,
human-readable descriptions of the dependency chain and the purpose of
each prerequisite series, rather than relying solely on lore links.

I appreciate the guidance and will incorporate this in the next revision.

Thanks,
Prasad