[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <57a02e71-06f7-402b-9ec8-def5020d5ea0@sirena.org.uk>
Date: Fri, 9 Jun 2023 14:13:34 +0100
From: Mark Brown <broonie@...nel.org>
To: NĂcolas F. R. A. Prado
<nfraprado@...labora.com>
Cc: kernel@...labora.com,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>,
Chen-Yu Tsai <wenst@...omium.org>,
Jaroslav Kysela <perex@...ex.cz>,
Liam Girdwood <lgirdwood@...il.com>,
Matthias Brugger <matthias.bgg@...il.com>,
Takashi Iwai <tiwai@...e.com>, alsa-devel@...a-project.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH] Revert "ASoC: mediatek: mt8192-mt6359: Remove " Jack"
from Headphone pin name"
On Fri, Jun 09, 2023 at 09:08:47AM -0400, NĂcolas F. R. A. Prado wrote:
> On Fri, Jun 09, 2023 at 10:39:25AM +0100, Mark Brown wrote:
> > Please submit patches using subject lines reflecting the style for the
> > subsystem, this makes it easier for people to identify relevant patches.
> > Look at what existing commits in the area you're changing are doing and
> > make sure your subject lines visually resemble what they're doing.
> > There's no need to resubmit to fix this alone.
> just for my own reference in the future, what exactly should have been done
> differently in this commit? Are the subject line and commit reference in the
> message generated by 'git revert' no good? Or is this message from a bot that
> can't handle revert commits?
Yes, what git revert generates by default are no good and you should
edit it to look like a normal commit message with a standard subject
line and standard way of referencing other commits.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists