| Message ID | 20230518072753.7361-1-krzysztof.kozlowski@linaro.org |
|---|---|
| Headers | show |
| Series | ASoC: codecs: do not store status in state containe | expand |
On Thu, May 18, 2023 at 09:27:41AM +0200, Krzysztof Kozlowski wrote: > Hi, > > Resend due to missing cover letter, so adding per-series tags was > not possible. Please write proper cover letters, but don't resend for this. You constantly raise small review errors in other people's submissions...
On 18/05/2023 12:23, Mark Brown wrote: > On Thu, May 18, 2023 at 09:27:41AM +0200, Krzysztof Kozlowski wrote: >> Hi, >> >> Resend due to missing cover letter, so adding per-series tags was >> not possible. > > Please write proper cover letters, but don't resend for this. You > constantly raise small review errors in other people's submissions... Since you asked for a cover letter and you did not apply the patchset (I checked in your tree), that seemed like a feedback for something you want me to fix. If you want to give feedback which person should not immediately fix, please state it explicitly or through applying patches. If you give imprecise messages, don't be surprised you receive different results. Best regards, Krzysztof
On Thu, 18 May 2023 09:27:41 +0200, Krzysztof Kozlowski wrote: > Resend due to missing cover letter, so adding per-series tags was > not possible. > > Added Rb tag. > > Best regards, > Krzysztof > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [01/12] ASoC: codecs: rt1308: do not store status in state container commit: cc3ff544a296b5b4bb021f4dc415b53a6955b980 [02/12] ASoC: codecs: rt1316: do not store status in state container commit: 70207b95b2245502496443475c9fc4eb72ba3b66 [03/12] ASoC: codecs: rt1318: do not store status in state container commit: 28eb1e4224c3b3ff29fe4c29bcdc011d3a0ffd07 [04/12] ASoC: codecs: rt5682: do not store status in state container commit: 758665b15acc1adb21a833c6456746ffbce07ed7 [05/12] ASoC: codecs: rt700: do not store status in state container commit: 9564c9f691128bc2dc69de02f7eed205d9b2513f [06/12] ASoC: codecs: rt711-sdca: do not store status in state container commit: 8322947e9228ef7f8c3dd13822d32c491f9488e7 [07/12] ASoC: codecs: rt711: do not store status in state container commit: 22e15c18b4a91c71bf66de06187b8a3199bb8cad [08/12] ASoC: codecs: rt712-sdca-dmic: do not store status in state container commit: d7a79616fc723305094fd7391085428b7a893636 [09/12] ASoC: codecs: rt712-sdca: do not store status in state container commit: 5cd02f96f49a7e6d2f8b96ddc42092776b554873 [10/12] ASoC: codecs: rt715-sdca: do not store status in state container commit: cda72c89d082f5953fab9948fc1212ca0df11d96 [11/12] ASoC: codecs: rt715: do not store status in state container commit: 0315dac5406c9c0b8e334195aa01c4ec155adf47 [12/12] ASoC: codecs: rt722-sdca: do not store status in state container commit: b932f21f6678659bd434c0d47e3bebc94bae0a51 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. Thanks, Mark
On Thu, May 18, 2023 at 12:33:17PM +0200, Krzysztof Kozlowski wrote: > On 18/05/2023 12:23, Mark Brown wrote: > > Please write proper cover letters, but don't resend for this. You > > constantly raise small review errors in other people's submissions... > Since you asked for a cover letter and you did not apply the patchset (I > checked in your tree), that seemed like a feedback for something you > want me to fix. > If you want to give feedback which person should not immediately fix, > please state it explicitly or through applying patches. > If you give imprecise messages, don't be surprised you receive different > results. I should not need to explain to you that a cover letter should have some useful description of the patch series it is a cover letter for, there's a degree of obviousnes one should expect to be understood especially by someone who is clearly very aware of kernel processes.