linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luca Coelho <luca@coelho.fi>
To: Sasha Levin <sashal@kernel.org>,
	Mordechay Goodstein <mordechay.goodstein@intel.com>,
	kvalo@codeaurora.org
Cc: linux-wireless@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2 v5.7 2/6] iwlwifi: mvm: beacon statistics shouldn't go backwards
Date: Tue, 21 Apr 2020 23:13:48 +0300	[thread overview]
Message-ID: <2e47b8a5826591461247e6247a9a158c9ed62973.camel@coelho.fi> (raw)
In-Reply-To: <20200421195610.21AD4206D9@mail.kernel.org>

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.


  reply	other threads:[~2020-04-21 20:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-17  7:08 [PATCH v2 v5.7 0/6] iwlwifi: fixes intended for v5.7 2020-04-03-2 Luca Coelho
2020-04-17  7:08 ` [PATCH v2 v5.7 1/6] iwlwifi: pcie: actually release queue memory in TVQM Luca Coelho
2020-04-21 12:40   ` Kalle Valo
2020-04-17  7:08 ` [PATCH v2 v5.7 2/6] iwlwifi: mvm: beacon statistics shouldn't go backwards Luca Coelho
2020-04-21 19:56   ` Sasha Levin
2020-04-21 20:13     ` Luca Coelho [this message]
2020-04-17  7:08 ` [PATCH v2 v5.7 3/6] iwlwifi: pcie: indicate correct RB size to device Luca Coelho
2020-04-17  7:08 ` [PATCH v2 v5.7 4/6] iwlwifi: mvm: limit maximum queue appropriately Luca Coelho
2020-04-21 19:56   ` Sasha Levin
2020-04-21 20:14     ` Luca Coelho
2020-04-17  7:08 ` [PATCH v2 v5.7 5/6] iwlwifi: mvm: Do not declare support for ACK Enabled Aggregation Luca Coelho
2020-04-21 19:56   ` Sasha Levin
2020-04-21 20:13     ` Luca Coelho
2020-04-21 20:55       ` Sasha Levin
2020-04-17  7:08 ` [PATCH v2 v5.7 6/6] iwlwifi: mvm: fix inactive TID removal return value usage Luca Coelho

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2e47b8a5826591461247e6247a9a158c9ed62973.camel@coelho.fi \
    --to=luca@coelho.fi \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mordechay.goodstein@intel.com \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).