All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-wireless@vger.kernel.org,
	Troy Tan <troy_tan@realsil.com.cn>,
	Larry Finger <Larry.Finger@lwfinger.net>,
	Stable <stable@vger.kernel.org>
Subject: Re: [RESEND, 1/2] rtlwifi: rtl8192ee: Fix handling of new style descriptors
Date: Fri,  6 Feb 2015 06:37:13 +0000 (UTC)	[thread overview]
Message-ID: <20150206063713.C8380140C14@smtp.codeaurora.org> (raw)
In-Reply-To: <1422983718-21432-2-git-send-email-Larry.Finger@lwfinger.net>


> From: Troy Tan <troy_tan@realsil.com.cn>
> 
> The hardware and firmware for the RTL8192EE utilize a FIFO list of
> descriptors. There were some problems with the initial implementation.
> The worst of these failed to detect that the FIFO was becoming full,
> which led to the device needing to be power cycled. As this condition
> is not relevant to most of the devices supported by rtlwifi, a callback
> routine was added to detect this situation. This patch implements the
> necessary changes in the pci handler, and the linkage into the appropriate
> rtl8192ee routine.
> 
> Signed-off-by: Troy Tan <troy_tan@realsil.com.cn>
> Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
> Cc: Stable <stable@vger.kernel.org> [V3.18]

Thanks, 2 patches applied to wireless-drivers-next.git:

d0311314d002 rtlwifi: rtl8192ee: Fix handling of new style descriptors
6d4beca37752 rtlwifi: rtl8192ee: Fix problems with calculating free space in FIFO

Kalle Valo

  reply	other threads:[~2015-02-06  6:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-03 17:15 [PATCH RESEND 0/2] Resend critical patches for rtl8192ee Larry Finger
2015-02-03 17:15 ` [PATCH RESEND 1/2] rtlwifi: rtl8192ee: Fix handling of new style descriptors Larry Finger
2015-02-06  6:37   ` Kalle Valo [this message]
2015-02-03 17:15 ` [PATCH RESEND 2/2] rtlwifi: rtl8192ee: Fix problems with calculating free space in FIFO 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=20150206063713.C8380140C14@smtp.codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=troy_tan@realsil.com.cn \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.