netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Adam Lee <adam.lee@canonical.com>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	Larry Finger <Larry.Finger@lwfinger.net>,
	"John W. Linville" <linville@tuxdriver.com>,
	Chaoming Li <chaoming_li@realsil.com.cn>,
	stable@vger.kernel.org
Subject: Re: [PATCH] rtlwifi: rtl8188ee: enable MSI interrupts support
Date: Sun, 23 Mar 2014 23:12:01 -0700	[thread overview]
Message-ID: <20140324061201.GA30798@kroah.com> (raw)
In-Reply-To: <20140324060512.GA3657@adam-laptop>

On Mon, Mar 24, 2014 at 02:05:21PM +0800, Adam Lee wrote:
> On Mon, Mar 24, 2014 at 02:00:41PM +0800, Adam Lee wrote:
> > Some HP notebooks using this rtl8188ee hardware module can't get
> > AP scan results with pin-based interrupts, enabling MSI interrupts could
> > fix it.
> > 
> > Signed-off-by: Adam Lee <adam.lee@canonical.com>
> > ---
> >  drivers/net/wireless/rtlwifi/rtl8188ee/sw.c | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/drivers/net/wireless/rtlwifi/rtl8188ee/sw.c b/drivers/net/wireless/rtlwifi/rtl8188ee/sw.c
> > index 347af1e..1b4101b 100644
> > --- a/drivers/net/wireless/rtlwifi/rtl8188ee/sw.c
> > +++ b/drivers/net/wireless/rtlwifi/rtl8188ee/sw.c
> > @@ -93,6 +93,7 @@ int rtl88e_init_sw_vars(struct ieee80211_hw *hw)
> >  	u8 tid;
> >  
> >  	rtl8188ee_bt_reg_init(hw);
> > +	rtlpci->msi_support = true;
> >  
> >  	rtlpriv->dm.dm_initialgain_enable = 1;
> >  	rtlpriv->dm.dm_flag = 0;
> > -- 
> > 1.9.1
> 
> Cc: stable@vger.kernel.org


<formletter>

This is not the correct way to submit patches for inclusion in the
stable kernel tree.  Please read Documentation/stable_kernel_rules.txt
for how to do this properly.

</formletter>

  reply	other threads:[~2014-03-24  6:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-24  6:00 [PATCH] rtlwifi: rtl8188ee: enable MSI interrupts support Adam Lee
     [not found] ` <1395640841-14477-1-git-send-email-adam.lee-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
2014-03-24  6:05   ` Adam Lee
2014-03-24  6:12     ` Greg KH [this message]
2014-03-24 11:34 ` [PATCH] rtlwifi: add " Adam Lee
     [not found]   ` <1395660884-15042-1-git-send-email-adam.lee-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
2014-03-24 11:49     ` Adam Lee
2014-03-25  2:48     ` [PATCH v2] " Adam Lee
     [not found]       ` <1395715732-9545-1-git-send-email-adam.lee-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
2014-03-27 18:15         ` John W. Linville
2014-03-27 18:45           ` Larry Finger
2014-03-28  3:36       ` [PATCH v3 1/2] rtlwifi: add MSI interrupts mode support Adam Lee
     [not found]         ` <1395977779-16093-1-git-send-email-adam.lee-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
2014-03-28  3:36           ` [PATCH v3 2/2] rtlwifi: rtl8188ee: enable MSI interrupts mode Adam Lee
2014-03-24 15:14   ` [PATCH] rtlwifi: add MSI interrupts support Larry Finger
     [not found]     ` <53304BBE.6040403-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2014-03-25  9:13       ` Adam Lee

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=20140324061201.GA30798@kroah.com \
    --to=greg@kroah.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=adam.lee@canonical.com \
    --cc=chaoming_li@realsil.com.cn \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.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).