From: "Tomas Winkler" <tomasw@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: davem@davemloft.net, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: pull request: wireless-2.6 2008-08-01
Date: Sat, 2 Aug 2008 12:16:47 +0300 [thread overview]
Message-ID: <1ba2fa240808020216i320e97e6j9510597f5b3daf83@mail.gmail.com> (raw)
In-Reply-To: <20080802032946.GA29921@tuxdriver.com>
On Sat, Aug 2, 2008 at 6:29 AM, John W. Linville <linville@tuxdriver.com> wrote:
> On Sat, Aug 02, 2008 at 12:43:32AM +0300, Tomas Winkler wrote:
>> On Fri, Aug 1, 2008 at 11:58 PM, John W. Linville
>> <linville@tuxdriver.com> wrote:
>> > Dave,
>> >
>> > Another big batch of wireless fixes for 2.6.27. The ath5k series is
>> > more than fixes, but I included it because it enables new ath5k
>> > hardware. (The ath5k.h changes in particular are documentation cleanups
>> > for registers based on info gleaned from the newly posted ath9k driver.)
>> > The others patches are fixes, some more obvious than others. :-)
>> >
>> > Let me know if there are any problems!
>>
>> All the iwlwifi patches should go up otherwise the support for 5000 HW
>> will be incomplete.
>
> Then they should have been posted before 2.6.26 was released...
Unfortunately I cannot align development progress with kernel
releases. This cat is not tatural for the driver. But this time all
the patches that went out after 2.6.26 are bug fixes maybe except
module renaming patches. There are no new features added all we do is
cleaning up our bug reports.
Hope we won't end up with not working driver like in 2.6.26.
Tomas
> --
> John W. Linville
> linville@tuxdriver.com
>
next prev parent reply other threads:[~2008-08-02 9:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-01 20:58 John W. Linville
2008-08-01 21:43 ` Tomas Winkler
2008-08-02 3:29 ` John W. Linville
2008-08-02 9:16 ` Tomas Winkler [this message]
2008-08-02 5:16 ` David Miller
2008-08-02 5:42 ` Ivo van Doorn
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=1ba2fa240808020216i320e97e6j9510597f5b3daf83@mail.gmail.com \
--to=tomasw@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@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
all inboxes | Powered by JetHome®