From: "John W. Linville" <linville@tuxdriver.com>
To: Michael Buesch <mb@bu3sch.de>
Cc: gregkh@suse.de, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] crap/rtl8187se: Fix comment-out-typo
Date: Mon, 10 Aug 2009 10:59:26 -0400 [thread overview]
Message-ID: <20090810145925.GA2733@tuxdriver.com> (raw)
In-Reply-To: <200908091802.31166.mb@bu3sch.de>
On Sun, Aug 09, 2009 at 06:02:30PM +0200, Michael Buesch wrote:
> This fixes a comment-out-typo that resulted in a dangling if-branch.
>
> Signed-off-by: Michael Buesch <mb@bu3sch.de>
>
> ---
>
> Completely untested, but looks sane.
>
>
> drivers/staging/rtl8187se/r8180_core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- wireless-testing.orig/drivers/staging/rtl8187se/r8180_core.c
> +++ wireless-testing/drivers/staging/rtl8187se/r8180_core.c
> @@ -3394,21 +3394,21 @@ short rtl8180_tx(struct net_device *dev,
> if(remain == 4 && i+4 >= buflen) break;
> /* ensure the last desc has at least 4 bytes payload */
>
> }
> txbuf = txbuf + i;
> *(tail+3)=*(tail+3) &~ 0xfff;
> *(tail+3)=*(tail+3) | i; // buffer lenght
> // Use short preamble or not
> if (priv->ieee80211->current_network.capability&WLAN_CAPABILITY_SHORT_PREAMBLE)
> if (priv->plcp_preamble_mode==1 && rate!=0) // short mode now, not long!
> - // *tail |= (1<<16); // enable short preamble mode.
> + ;// *tail |= (1<<16); // enable short preamble mode.
>
> #ifdef CONFIG_RTL8185B
> if(bCTSEnable) {
> *tail |= (1<<18);
> }
>
> if(bRTSEnable) //rts enable
> {
> *tail |= ((ieeerate2rtlrate(priv->ieee80211->basic_rate))<<19);//RTS RATE
> *tail |= (1<<23);//rts enable
Thanks for the reminder of why rtl8187se remains abandoned...
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2009-08-10 15:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-09 16:02 [PATCH] crap/rtl8187se: Fix comment-out-typo Michael Buesch
2009-08-10 14:59 ` John W. Linville [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=20090810145925.GA2733@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=gregkh@suse.de \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
/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).