[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6963ab04-d0d2-42ee-9fc3-19f9c298849b@sirena.org.uk>
Date: Tue, 7 Oct 2025 13:10:12 +0100
From: Mark Brown <broonie@...nel.org>
To: Sune Brian <briansune@...il.com>
Cc: Liam Girdwood <lgirdwood@...il.com>,
Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>,
linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org,
Charles Keepax <ckeepax@...nsource.cirrus.com>
Subject: Re: [PATCH v2] ASoC: wm8978: add missing BCLK divider setup
On Tue, Oct 07, 2025 at 07:56:31PM +0800, Sune Brian wrote:
> Mark Brown <broonie@...nel.org> 於 2025年10月7日 週二 下午7:52寫道:
> > > > Please don't send new patches in reply to old patches or serieses, this
> > > > makes it harder for both people and tools to understand what is going
> > > > on - it can bury things in mailboxes and make it difficult to keep track
> > > > of what current patches are, both for the new patches and the old ones.
> > The title is fine, the above is about sending the patch as a reply.
> Got it, when title amended version is sent, need no reply with
> previous revision ID.
No. You sent the new version as a reply to the prior verison which
nearly got it binned. You should send new versions as new threads, not
as replies to other serieses.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists