linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
	ipw2100-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, Zhu Yi <yi.zhu@intel.com>,
	James Ketrenos <jketreno@linux.intel.com>,
	Reinette Chatre <reinette.chatre@intel.com>
Subject: Re: [PATCH 1/1] ipw2200, fix ipw io functions
Date: Fri, 13 Feb 2009 10:44:14 -0500	[thread overview]
Message-ID: <1234539854.3173.6.camel@localhost> (raw)
In-Reply-To: <1234474180-910-1-git-send-email-jirislaby@gmail.com>

On Thu, 2009-02-12 at 22:29 +0100, Jiri Slaby wrote:
> - some of them are defined as follows:
>   #define ipw_write32	expr1; expr2
>   and are called from loops or ifs without a compound statement, so
>   they are broken. Fix it by putting them into do {} while (0) for
>   writes and ({ }) for reads.
> - also unify and cleanup them while at it -- convert them from
>   macros to inline functions, so that we get some basic typechecking
> 
> Signed-off-by: Jiri Slaby <jirislaby@gmail.com>
> Cc: Zhu Yi <yi.zhu@intel.com>
> Cc: James Ketrenos <jketreno@linux.intel.com>
> Cc: Reinette Chatre <reinette.chatre@intel.com>

I've been running with this patch for 15 hours or so and it works well
for me.  It may have even fixed random issues with the card crapping out
after resume (successful association, does DHCP, but after a minute or
two no longer passes traffic until a hard reboot even with multiple
rmmod/modprobe runs), though that could also be hallucination on my
part.

Dan



      parent reply	other threads:[~2009-02-13 15:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-12 21:29 [PATCH 1/1] ipw2200, fix ipw io functions Jiri Slaby
2009-02-13  0:49 ` Zhu Yi
2009-02-13  8:23   ` Jiri Slaby
2009-02-13  8:50     ` Zhu Yi
2009-02-13 15:44 ` Dan Williams [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=1234539854.3173.6.camel@localhost \
    --to=dcbw@redhat.com \
    --cc=ipw2100-devel@lists.sourceforge.net \
    --cc=jirislaby@gmail.com \
    --cc=jketreno@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=reinette.chatre@intel.com \
    --cc=yi.zhu@intel.com \
    /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).