From: "John W. Linville" <linville@tuxdriver.com>
To: Dave <kilroyd@googlemail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: correct typos in "unavailable upon resume" warning
Date: Sat, 20 Mar 2010 08:48:19 -0400 [thread overview]
Message-ID: <20100320124818.GA7255@tuxdriver.com> (raw)
In-Reply-To: <4BA49EE2.8000902@gmail.com>
On Sat, Mar 20, 2010 at 10:09:38AM +0000, Dave wrote:
> John W. Linville wrote:
> > Signed-off-by: John W. Linville <linville@tuxdriver.com>
> > ---
> > net/mac80211/util.c | 4 ++--
> > 1 files changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/net/mac80211/util.c b/net/mac80211/util.c
> > index c453226..a9d9098 100644
> > --- a/net/mac80211/util.c
> > +++ b/net/mac80211/util.c
> > @@ -1097,8 +1097,8 @@ int ieee80211_reconfig(struct ieee80211_local *local)
> > */
> > res = drv_start(local);
> > if (res) {
> > - WARN(local->suspended, "Harware became unavailable "
> > - "upon resume. This is could be a software issue"
> > + WARN(local->suspended, "Hardware became unavailable "
> > + "upon resume. This is could be a software issue "
>
> ^^
>
> As long as you're addressing that line, you probably want to lose the
> 'is'. Or the 'could be'.
Yes, thanks. Obviously I suck as a proof-reader...
John
--
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:[~2010-03-20 13:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 19:33 [PATCH] mac80211: correct typos in "unavailable upon resume" warning John W. Linville
2010-03-20 10:09 ` Dave
2010-03-20 12:48 ` 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=20100320124818.GA7255@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=kilroyd@googlemail.com \
--cc=linux-wireless@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).