From: "John W. Linville" <linville@tuxdriver.com>
To: Henning Habighorst <h.habighorst@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Questions regarding the rtl8180 driver (compared to zd1211rw driver)
Date: Mon, 28 Jan 2008 09:45:35 -0500 [thread overview]
Message-ID: <20080128144535.GA5835@tuxdriver.com> (raw)
In-Reply-To: <549e645c0801260335t56e18e75l6dd2c58b47e0257b@mail.gmail.com>
On Sat, Jan 26, 2008 at 12:35:56PM +0100, Henning Habighorst wrote:
> As I am not sure what information you'll need or if this is a "known"
> problem I would be happy for an answer, if I could help and if , how
> ;)
Henning,
Thanks for the email and your interest. However, I'm not really sure
what you are asking or reporting. :-)
I think it would be better if you were to focus on specific problems
with individual drivers. You probably want to confine those problem
reports to individual messages rather than putting all of them into
a single message.
Thanks for your participation!
John
--
John W. Linville
linville@tuxdriver.com
prev parent reply other threads:[~2008-01-28 15:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-26 11:35 Questions regarding the rtl8180 driver (compared to zd1211rw driver) Henning Habighorst
2008-01-28 14:45 ` 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=20080128144535.GA5835@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=h.habighorst@gmail.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).