From: David Miller <davem@davemloft.net>
To: linville@tuxdriver.com
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: pull request: wireless-2.6 'upstream' 2008-01-24
Date: Thu, 24 Jan 2008 21:26:27 -0800 (PST) [thread overview]
Message-ID: <20080124.212627.193699738.davem@davemloft.net> (raw)
In-Reply-To: <20080125035751.GC3411@tuxdriver.com>
From: "John W. Linville" <linville@tuxdriver.com>
Date: Thu, 24 Jan 2008 22:57:51 -0500
> On Thu, Jan 24, 2008 at 02:53:43PM -0500, John W. Linville wrote:
>
> > The cfg80211 API change breaks ath5k, so I have listed it as "depends
> > on BROKEN". I am assured that the ath5k team has agreed to fix
> > this ASAP. Meanwhile we wanted to have it in place so that we can
> > start shaking-out problems with other drivers.
>
> Looks like this might have broken more than I expected, and there
> may be some refactoring of the wireless rndis bits too. So, let's
> hold off on this request. I'll post a new one in the next day or so.
Ok.
prev parent reply other threads:[~2008-01-25 5:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-24 19:53 pull request: wireless-2.6 'upstream' 2008-01-24 John W. Linville
2008-01-25 3:57 ` John W. Linville
2008-01-25 5:26 ` David Miller [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=20080124.212627.193699738.davem@davemloft.net \
--to=davem@davemloft.net \
--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;
as well as URLs for NNTP newsgroup(s).