Message ID | 20230322135927.7668-1-peter.ujfalusi@linux.intel.com (mailing list archive) |
---|---|
Headers | show |
Series | ASoC: SOF: ipc4/intel: Support for ChainDMA | expand |
On Wed, Mar 22, 2023 at 03:59:24PM +0200, Peter Ujfalusi wrote: > Hi, > > Changes since v1: > - Fix missed mutex unlocking in sof_ipc4_widget_free() > Reported by Dan Carpenter (thank you!) Please do not submit new versions of already applied patches, please submit incremental updates to the existing code. Modifying existing commits creates problems for other users building on top of those commits so it's best practice to only change pubished git commits if absolutely essential.
On Wed, 2023-03-22 at 14:04 +0000, Mark Brown wrote: > On Wed, Mar 22, 2023 at 03:59:24PM +0200, Peter Ujfalusi wrote: > > Hi, > > > > Changes since v1: > > - Fix missed mutex unlocking in sof_ipc4_widget_free() > > Reported by Dan Carpenter (thank you!) > > Please do not submit new versions of already applied patches, please > submit incremental updates to the existing code. Modifying existing > commits creates problems for other users building on top of those > commits so it's best practice to only change pubished git commits if > absolutely essential. Hi Mark, Would a git fixup patch do at this phase, or should we do just a regular patch with Fixes: ca5ce0caa67fa9 ("ASoC: SOF: ipc4/intel: Add support for chained DMA") line? Best regards, Jyri --------------------------------------------------------------------- Intel Finland Oy Registered Address: PL 281, 00181 Helsinki Business Identity Code: 0357606 - 4 Domiciled in Helsinki This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
On Wed, Mar 22, 2023 at 03:15:23PM +0000, Sarha, Jyri wrote: > On Wed, 2023-03-22 at 14:04 +0000, Mark Brown wrote: > > Please do not submit new versions of already applied patches, please > > submit incremental updates to the existing code. Modifying existing > > commits creates problems for other users building on top of those > > commits so it's best practice to only change pubished git commits if > > absolutely essential. > Hi Mark, > Would a git fixup patch do at this phase, or should we do just a > regular patch with To repeat what's quoted above "please submit incremental updates to the existing code".
Hi Mark, On 22/03/2023 16:04, Mark Brown wrote: > On Wed, Mar 22, 2023 at 03:59:24PM +0200, Peter Ujfalusi wrote: >> Hi, >> >> Changes since v1: >> - Fix missed mutex unlocking in sof_ipc4_widget_free() >> Reported by Dan Carpenter (thank you!) > > Please do not submit new versions of already applied patches, please > submit incremental updates to the existing code. Modifying existing > commits creates problems for other users building on top of those > commits so it's best practice to only change pubished git commits if > absolutely essential. I'm aware of that and checked my mailbox several times that I don't have your applied notification mail. I would have sent a fix patch instead otherwise. Sorry for the inconvenience.