On Tue, 2020-04-21 at 19:56 +0000, Sasha Levin wrote:
> Hi
>
> [This is an automated email]
>
> This commit has been processed because it contains a -stable tag.
> The stable tag indicates that it's relevant for the following trees: 4.19+
>
> The bot has tested the following trees: v5.6.5, v5.5.18, v5.4.33, v4.19.116.
>
> v5.6.5: Build OK!
> v5.5.18: Build OK!
> v5.4.33: Build OK!
> v4.19.116: Failed to apply! Possible dependencies:
> 17b809c9b22e ("iwlwifi: dbg: move debug data to a struct")
> 22463857a16b ("iwlwifi: receive umac and lmac error table addresses from TLVs")
> 2d8c261511ab ("iwlwifi: add d3 debug data support")
> 33bdccb71aa6 ("iwlwifi: remove FSF's address from the license notice")
> 58d3bef4163b ("iwlwifi: remove all the d0i3 references")
> 68025d5f9bfe ("iwlwifi: dbg: refactor dump code to improve readability")
> 8d534e96b500 ("iwlwifi: dbg_ini: create new dump flow and implement prph dump")
> a6820511f193 ("iwlwifi: dbg: split iwl_fw_error_dump to two functions")
> ae17404e3860 ("iwlwifi: avoid code duplication in stopping fw debug data recording")
> c5f97542aa06 ("iwlwifi: change monitor DMA to be coherent")
> d25eec305c97 ("iwlwifi: fw: add a restart FW debug function")
> da7527173b18 ("iwlwifi: debug flow cleanup")
> ea7c2bfdec6d ("Revert "iwlwifi: allow memory debug TLV to specify the memory type"")
> f130bb75d881 ("iwlwifi: add FW recovery flow")
>
>
> NOTE: The patch will not be queued to stable trees until it is upstream.
>
> How should we proceed with this patch?
Same thing as with the other patches: We definitely don't want all
these dependencies. Some functions were moved around and that's what's
causing the failures. I'll rebase this patch for those kernels where
it failed and submit separately.
--
Luca.
