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, netdev@vger.kernel.org,
	"troy_tan@realsil.com.cn >> 谭杭波" <troy_tan@realsil.com.cn>
Subject: Re: [PATCH V2 for 3.19 0/7] Fixes for rtl8192ee
Date: Fri, 23 Jan 2015 22:24:10 +0200	[thread overview]
Message-ID: <87egqljled.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <54C27975.50501@lwfinger.net> (Larry Finger's message of "Fri, 23 Jan 2015 10:40:21 -0600")

Larry Finger <Larry.Finger@lwfinger.net> writes:

> It is too bad that it took so long to get these ready. I think the
> reason that there are not a lot of bug reports is because the
> complaints are all in the GitHub issues for the rtlwifi_new repo, or
> with Ubuntu. If there are any that get filed against Bugzilla, I will
> refer them to that repo.

Ok.

> Driver rtl8192ee was new in 3.18. There had been a previous version in
> staging, but it did not get a lot of usage. I'm not sure if the
> additional usage after 3.18 was due to the driver being in the regular
> tree, or if vendors started using the chips, but the problem reports
> started arriving. All these bugs have been part of rtl8192ee since it
> has been in the kernel, thus they are hard to categorize as
> regressions.

Good. So we are not going backwards in quality, that's most important.

> Push all 7 into -next so that they will be in 3.20. If you think it to
> be prudent, please leave the Cc for stable. That way 3.18 and 3.19
> will eventually get the fixes.

I think that's the best plan, thanks for understanding. The patches are
in my queue and I should apply them within the next few days, unless
anything comes during the review.

-- 
Kalle Valo

      reply	other threads:[~2015-01-23 20:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-20 17:01 [PATCH V2 for 3.19 0/7] Fixes for rtl8192ee Larry Finger
2015-01-20 17:01 ` Larry Finger
2015-01-20 17:01 ` [PATCH V2 for 3.19 1/7] rtlwifi: Remove logging statement that is no longer needed Larry Finger
2015-01-20 17:01   ` Larry Finger
2015-02-10 14:10   ` [V2, for, 3.19, " Kalle Valo
2015-01-20 17:01 ` [PATCH V2 for 3.19 2/7] rtlwifi: rtl8192ee: Fix handling of new style descriptors Larry Finger
2015-01-20 17:01 ` [PATCH V2 for 3.19 3/7] rtlwifi: rtl8192ee: Fix adhoc fail Larry Finger
2015-01-20 17:01   ` Larry Finger
2015-02-03 13:15   ` [V2,for,3.19,3/7] " Kalle Valo
2015-02-03 13:23     ` Kalle Valo
2015-02-03 16:00       ` Larry Finger
2015-01-20 17:01 ` [PATCH V2 for 3.19 4/7] rtlwifi: rtl8192ee: Fix TX hang due to failure to update TX write point Larry Finger
2015-01-20 17:01   ` Larry Finger
2015-01-20 17:01 ` [PATCH V2 for 3.19 5/7] rtlwifi: rtl8192ee: Fix parsing of received packet Larry Finger
2015-01-20 17:01 ` [PATCH V2 for 3.19 6/7] rtlwifi: rtl8192ee: Fix problems with calculating free space in FIFO Larry Finger
2015-01-20 17:01 ` [PATCH V2 for 3.19 7/7] rtlwifi: rtl8192ee: Fix DMA stalls Larry Finger
2015-01-23 15:26 ` [PATCH V2 for 3.19 0/7] Fixes for rtl8192ee Kalle Valo
2015-01-23 16:40   ` Larry Finger
2015-01-23 20:24     ` Kalle Valo [this message]

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=87egqljled.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@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.