linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Sasha Levin <sashal@kernel.org>, kvalo@codeaurora.org
Cc: linux-wireless@vger.kernel.org, pkshih@realtek.com,
	stable@vger.kernel.org
Subject: Re: [PATCH 2/3] rtlwifi: rtl8192de: Fix missing callback that tests for hw release of buffer
Date: Fri, 22 Nov 2019 11:59:01 -0600	[thread overview]
Message-ID: <abb85c02-d7f2-7eb0-7522-7616d32de100@lwfinger.net> (raw)
In-Reply-To: <20191122070014.BA0492070A@mail.kernel.org>

On 11/22/19 1:00 AM, Sasha Levin wrote:
> Hi,
> 
> [This is an automated email]
> 
> This commit has been processed because it contains a "Fixes:" tag,
> fixing commit: 38506ecefab9 ("rtlwifi: rtl_pci: Start modification for new drivers").
> 
> The bot has tested the following trees: v5.3.11, v4.19.84, v4.14.154, v4.9.201, v4.4.201.
> 
> v5.3.11: Build OK!
> v4.19.84: Build OK!
> v4.14.154: Failed to apply! Possible dependencies:
>      0c07bd745760 ("rtlwifi: rtl8192ee: Make driver support 64bits DMA.")
> 
> v4.9.201: Failed to apply! Possible dependencies:
>      004a1e167905 ("rtlwifi: rtl8821ae: Remove all instances of DBG_EMERG")
>      02527a73beb3 ("rtlwifi: rtl8188ee: Remove all instances of DBG_EMERG")
>      0c07bd745760 ("rtlwifi: rtl8192ee: Make driver support 64bits DMA.")
>      102e295ed5a4 ("rtlwifi: Redo debugging macros RTPRINT and RT_PRINT_DATA")
>      2d15acac2354 ("rtlwifi: rtl8192se: Remove all instances of DBG_EMERG")
>      4e2b4378f9d7 ("rtlwifi: rtl8723be: Remove all instances of DBG_EMERG")
>      a44f59d60365 ("rtlwifi: rtl8192ee: Remove all instances of DBG_EMERG")
>      a67005bc46d9 ("rtlwifi: rtl8723ae: Remove all instances of DBG_EMERG")
>      b8c79f454880 ("rtlwifi: rtl8192de: Remove all instances of DBG_EMERG")
>      c34df318ec9f ("rtlwifi: Convert COMP_XX entries into a proper debugging mask")
>      c38af3f06af4 ("rtlwifi: rtl8192cu: Remove all instances of DBG_EMERG")
>      e40a005652ad ("rtlwifi: rtl8192ce: Remove all instances of DBG_EMERG")
> 
> v4.4.201: Failed to apply! Possible dependencies:
>      02527a73beb3 ("rtlwifi: rtl8188ee: Remove all instances of DBG_EMERG")
>      0c07bd745760 ("rtlwifi: rtl8192ee: Make driver support 64bits DMA.")
>      102e295ed5a4 ("rtlwifi: Redo debugging macros RTPRINT and RT_PRINT_DATA")
>      4713bd1c7407 ("rtlwifi: Add missing newlines to RT_TRACE calls")
>      5345ea6a4bfb ("rtlwifi: fix error handling in *_read_adapter_info()")
>      9ce221915a94 ("rtlwifi: Create _rtl_dbg_trace function to reduce RT_TRACE code size")
>      ad5748893b27 ("rtlwifi: Add switch variable to 'switch case not processed' messages")
>      b8c79f454880 ("rtlwifi: rtl8192de: Remove all instances of DBG_EMERG")
>      c34df318ec9f ("rtlwifi: Convert COMP_XX entries into a proper debugging mask")
>      c38af3f06af4 ("rtlwifi: rtl8192cu: Remove all instances of DBG_EMERG")
>      e40a005652ad ("rtlwifi: rtl8192ce: Remove all instances of DBG_EMERG")
> 
> 
> NOTE: The patch will not be queued to stable trees until it is upstream.
> 
> How should we proceed with this patch?

Sasha,

The underlying directories were moved from drivers/net/wireless/rtlwifi/ to 
drivers/net/wireless/realtek/rtlwifi/. I can refactor the patches to account for 
this change. How should I annotate them, and where should I send them?

Larry


  parent reply	other threads:[~2019-11-22 17:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-11 19:40 [PATCH 0/3] rtlwifi: rtl8192de: Fixes for several regressions Larry Finger
2019-11-11 19:40 ` [PATCH 1/3] rtlwifi: rtl8192de: Fix missing code to retrieve RX buffer address Larry Finger
2019-11-14 15:10   ` Kalle Valo
2019-11-11 19:40 ` [PATCH 2/3] rtlwifi: rtl8192de: Fix missing callback that tests for hw release of buffer Larry Finger
     [not found]   ` <20191122070014.BA0492070A@mail.kernel.org>
2019-11-22 17:59     ` Larry Finger [this message]
2019-11-11 19:40 ` [PATCH 3/3] rtlwifi: rtl8192de: Fix missing enable interrupt flag Larry Finger

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=abb85c02-d7f2-7eb0-7522-7616d32de100@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkshih@realtek.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).