From: Dan Williams <dcbw@redhat.com>
To: Markus Becker <mab@comnets.uni-bremen.de>
Cc: David Woodhouse <David@Woodhou.se>,
Holger Schurig <hs4233@mail.mn-solutions.de>,
linux-wireless@vger.kernel.org,
John Daiker <daikerjohn@gmail.com>,
"John W. Linville" <linville@tuxdriver.com>,
julian.calaby@gmail.com, andreamrl@tiscali.it
Subject: Re: Update: [RFC][PATCH] mrv8k: Driver for "Marvell 88w8335 [Libertas]"
Date: Fri, 09 May 2008 12:25:46 -0400 [thread overview]
Message-ID: <1210350346.23925.0.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0805091604230.24384@bugs.comnets.uni-bremen.de>
On Fri, 2008-05-09 at 16:10 +0200, Markus Becker wrote:
> Hi,
>
> I have just pushed the mrv8k patch sent to the mailing list to
> git://git.infradead.org/mrv8k-2.6.git.
Awesome. Will work from that.
Dan
> Markus
>
> On Thu, 8 May 2008, Dan Williams wrote:
>
> > On Thu, 2008-05-08 at 16:02 +0100, David Woodhouse wrote:
> >> On Thu, 2008-05-08 at 10:43 -0400, Dan Williams wrote:
> >>> Yeah, I'll get David to make a git tree. You should still ask for an
> >>> account and send him your SSH key so that you can push to the tree as
> >>> well.
> >>
> >> I've created git://git.infradead.org/mrv8k.git and the mrv8k group,
> >> which has schurig,mab,dwmw2,dcbw in it.
> >>
> >> I'm a little confused by the request, because I thought wireless
> >> development was stuck in the 1990s and didn't use git -- I thought it
> >> was done by patches. But I'll let you work that one out for
> >> yourselves. :)
> >
> > We've got a ways to go before we can upstream the driver. There's still
> > quite a bit of cleanup to do. Best to do that with a git tree first
> > before submitting the cleaned up patch set.
> >
> > Dan
> >
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-05-09 16:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-19 10:00 Marvell 88w8335 [Libertas] Markus Becker
2008-03-19 10:24 ` Holger Schurig
2008-03-20 8:16 ` Markus Becker
2008-03-28 13:36 ` [RFC][PATCH] mrv8k: Driver for "Marvell 88w8335 [Libertas]" Markus Becker
2008-03-28 13:51 ` Dan Williams
2008-03-29 11:37 ` Andrea Merello
2008-03-31 19:39 ` Dan Williams
2008-04-01 13:58 ` Markus Becker
2008-04-03 7:25 ` Update: " Markus Becker
2008-04-08 15:56 ` Dan Williams
2008-04-11 19:55 ` Dan Williams
2008-04-14 7:35 ` Markus Becker
2008-04-24 17:13 ` Dan Williams
2008-04-24 17:21 ` David Woodhouse
2008-05-07 18:23 ` John Daiker
2008-05-08 7:12 ` Holger Schurig
2008-05-08 8:28 ` Markus Becker
2008-05-08 14:43 ` Dan Williams
2008-05-08 15:02 ` David Woodhouse
2008-05-08 17:45 ` Dan Williams
2008-05-09 14:10 ` Markus Becker
2008-05-09 16:25 ` Dan Williams [this message]
2008-03-19 11:49 ` Marvell 88w8335 [Libertas] Julian Calaby
2008-04-01 16:33 ` Albert Cahalan
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=1210350346.23925.0.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=David@Woodhou.se \
--cc=andreamrl@tiscali.it \
--cc=daikerjohn@gmail.com \
--cc=hs4233@mail.mn-solutions.de \
--cc=julian.calaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mab@comnets.uni-bremen.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.