netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefano Brivio <stefano.brivio@polimi.it>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: netdev@vger.kernel.org
Subject: Re: Wireless patches to push for 2.6.18?
Date: Sun, 28 May 2006 07:37:32 +0000 (UTC)
Date: Fri, 27 Apr 2007 10:15:19 +0200	[thread overview]
Message-ID: <20070427101519.28e4bed7@localhost> (raw)
In-Reply-To: <20060526195855.GD32487@tuxdriver.com>

On Fri, 26 May 2006 15:59:00 -0400
"John W. Linville" <linville@tuxdriver.com> wrote:

> Anyone have anything else they are holding-back for 2.6.18?

We would like to get PCI-E support patchset into bcm43xx driver as well,
but we are still testing it. I hope we'll be ready in a few days.


--
Ciao
Stefano

      parent reply	other threads:[~2006-05-28  7:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-26 19:59 Wireless patches to push for 2.6.18? John W. Linville
2006-05-26 22:17 ` Michael Buesch
2006-05-28  7:37 ` Stefano Brivio [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=20070427101519.28e4bed7@localhost \
    --to=stefano.brivio@polimi.it \
    --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).