linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Masanari Iida <standby24x7@gmail.com>
Cc: dsd@gentoo.org, kune@deine-taler.de,
	linux-wireless@vger.kernel.org, trivial@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [trivial] zd1211rw: Fix typo in zd_usb.c and zd_mac.c
Date: Wed, 22 Feb 2012 15:03:12 -0500	[thread overview]
Message-ID: <20120222200311.GA28075@tuxdriver.com> (raw)
In-Reply-To: <20120222193039.GC822@tuxdriver.com>

Sorry, I misread the patch -- I'm having a bad week...

On Wed, Feb 22, 2012 at 02:30:39PM -0500, John W. Linville wrote:
> NAK
> 
> http://mw1.merriam-webster.com/dictionary/resetting
> 
> On Fri, Feb 10, 2012 at 12:29:32AM +0900, Masanari Iida wrote:
> > Correct spelling "reseting" to "resetting" in
> > drivers/net/wireless/zd1211rw/zd_usb.c
> > drivers/net/wireless/zd1211rw/zd_mac.c
> > 
> > Signed-off-by: Masanari Iida <standby24x7@gmail.com>
> > ---
> >  drivers/net/wireless/zd1211rw/zd_mac.c |    2 +-
> >  drivers/net/wireless/zd1211rw/zd_usb.c |    2 +-
> >  2 files changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/drivers/net/wireless/zd1211rw/zd_mac.c b/drivers/net/wireless/zd1211rw/zd_mac.c
> > index 0a70149..a8370eb 100644
> > --- a/drivers/net/wireless/zd1211rw/zd_mac.c
> > +++ b/drivers/net/wireless/zd1211rw/zd_mac.c
> > @@ -846,7 +846,7 @@ reset_device:
> >  
> >  	/* semaphore stuck, reset device to avoid fw freeze later */
> >  	dev_warn(zd_mac_dev(mac), "CR_BCN_FIFO_SEMAPHORE stuck, "
> > -				  "reseting device...");
> > +				  "resetting device...");
> >  	usb_queue_reset_device(mac->chip.usb.intf);
> >  
> >  	return r;
> > diff --git a/drivers/net/wireless/zd1211rw/zd_usb.c b/drivers/net/wireless/zd1211rw/zd_usb.c
> > index 785bdbe..f766b3e 100644
> > --- a/drivers/net/wireless/zd1211rw/zd_usb.c
> > +++ b/drivers/net/wireless/zd1211rw/zd_usb.c
> > @@ -1104,7 +1104,7 @@ static void zd_tx_watchdog_handler(struct work_struct *work)
> >  		goto out;
> >  
> >  	/* TX halted, try reset */
> > -	dev_warn(zd_usb_dev(usb), "TX-stall detected, reseting device...");
> > +	dev_warn(zd_usb_dev(usb), "TX-stall detected, resetting device...");
> >  
> >  	usb_queue_reset_device(usb->intf);
> >  
> > -- 
> > 1.7.6.5
> > 
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
> > 
> 
> -- 
> John W. Linville		Someday the world will need a hero, and you
> linville@tuxdriver.com			might be all we have.  Be ready.

-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

      reply	other threads:[~2012-02-22 20:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-09 15:29 [PATCH] [trivial] zd1211rw: Fix typo in zd_usb.c and zd_mac.c Masanari Iida
2012-02-22 19:30 ` John W. Linville
2012-02-22 20:03   ` 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=20120222200311.GA28075@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=dsd@gentoo.org \
    --cc=kune@deine-taler.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=standby24x7@gmail.com \
    --cc=trivial@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).