[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zj27LHKXSFXx_6G2@finisterre.sirena.org.uk>
Date: Fri, 10 May 2024 07:14:04 +0100
From: Mark Brown <broonie@...nel.org>
To: Shenghao Ding <shenghao-ding@...com>
Cc: andriy.shevchenko@...ux.intel.com, lgirdwood@...il.com, perex@...ex.cz,
pierre-louis.bossart@...ux.intel.com, 13916275206@....com,
alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
liam.r.girdwood@...el.com, bard.liao@...el.com,
yung-chuan.liao@...ux.intel.com, kevin-lu@...com,
cameron.berkenpas@...il.com, tiwai@...e.de, baojun.xu@...com,
soyer@....hu, Baojun.Xu@....com
Subject: Re: [PATCH v4 2/3] ALSA: ASoc/tas2781: Fix wrong loading calibrated
data sequence
On Fri, May 10, 2024 at 11:41:20AM +0800, Shenghao Ding wrote:
> - Divide one patch into two individual patches. compiling warning patch
> has been upstream in another patch (Fixes: 1ae14f3520b1 ("ASoC: tas2781:
> Fix a warning reported by robot kernel test"))
Oh, I see what's going on - when you split a patch up into several
patches each individual patch needs to have it's own changelog
describing what's going on in that specific patch. If you just
replicate the changelog you had for the original patch into each of the
split patches it will inevitably not describe the separated out patches
well.
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.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists