From: Jason Riedy <jason@acm.org>
To: "Tomas Winkler" <tomasw@gmail.com>
Cc: ipw3945-devel@lists.sourceforge.net, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] Remove most references to iwl4965-only features from iwl3945.
Date: Wed, 02 Apr 2008 14:22:29 -0700 [thread overview]
Message-ID: <87prt86jfu.fsf@sparse.dyndns.org> (raw)
In-Reply-To: <1ba2fa240804021250t4d0f3e12g201f1af253dea838@mail.gmail.com> (Tomas Winkler's message of "Wed, 2 Apr 2008 22:50:31 +0300")
And Tomas Winkler writes:
> This one is not supported in 3945 for real.
Someone with access to the documentation should rip the 4965-only
pieces out of the 3945-only driver...
Jason
next prev parent reply other threads:[~2008-04-02 21:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-02 6:26 [PATCH] Remove most references to iwl4965-only features from iwl3945 Jason Riedy
2008-04-02 19:50 ` Tomas Winkler
2008-04-02 21:22 ` Jason Riedy [this message]
2008-04-02 23:38 ` Chatre, Reinette
2008-04-08 18:01 ` [ipw3945-devel] " John W. Linville
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=87prt86jfu.fsf@sparse.dyndns.org \
--to=jason@acm.org \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=tomasw@gmail.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).