From: Patrick McHardy <kaber@trash.net>
To: "Luis R. Rodriguez" <mcgrof@winlab.rutgers.edu>
Cc: "David S. Miller" <davem@davemloft.net>,
linux-wireless@vger.kernel.org, Dan Williams <dcbw@redhat.com>,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: prism54: revert "prism54: set carrier flags correctly"
Date: Mon, 12 May 2008 18:55:39 +0200 [thread overview]
Message-ID: <4828768B.8020107@trash.net> (raw)
In-Reply-To: <43e72e890805120952q5abca0c3sfe49dedd97ed772e@mail.gmail.com>
Luis R. Rodriguez wrote:
> Patick, thanks for staying on top of this, however NACK. The fix I
> sumbitted and you tested should be merged. I nagged about it too, John
> just wanted a resubmit with a log message.
I'm happy either way, I just wanted to resurrect the interest in
this bug :)
prev parent reply other threads:[~2008-05-12 16:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 16:34 prism54: revert "prism54: set carrier flags correctly" Patrick McHardy
2008-05-12 16:52 ` Luis R. Rodriguez
2008-05-12 16:55 ` Luis R. Rodriguez
2008-05-12 16:55 ` Patrick McHardy [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=4828768B.8020107@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=dcbw@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@winlab.rutgers.edu \
/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).