From: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
To: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
Cc: jeff-o2qLIJkoznsdnm+yROfE0A@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
flamingice-R9e9/4HEdknk1uMJSBkQmQ@public.gmane.org
Subject: Re: Please pull 'adm8211' branch of wireless-2.6
Date: Sat, 15 Sep 2007 22:36:00 -0400 [thread overview]
Message-ID: <20070916023600.GA3967@tuxdriver.com> (raw)
In-Reply-To: <20070915.112549.79067357.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
On Sat, Sep 15, 2007 at 11:25:49AM -0700, David Miller wrote:
> From: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
> Date: Sat, 15 Sep 2007 13:00:18 -0400
>
> > Come to think of it, this driver will depend on some of the mac80211
> > patches Dave M. has queued for net-2.6.24. Perhaps it would be better
> > if Dave were to merge it with his tree?
> >
> > Jeff, if you have no objection then please sign-off/ack/whatever so
> > davem can see it. Dave, in that case please pull this to net-2.6.24.
>
> There are a lot of things to sort out :-)
>
> What I'm going to try and accomplish right now is:
>
> 1) Rebase my tree, I just finished that.
> 2) Integrate linville's upstream-davem stuff into net-2.6.24
> 3) Integrate Jeff's upstream branch into net-2.6.24
Forgot about this part...would you be doing this otherwise? If not,
I can rearrange this patch (or its successor) so that it is based
off your tree instead.
> 4) Integrate linville's adm8211 driver into net-2.6.24
>
> We'll see how well that goes.
It sounds like Michael will be respinning in response to Jeff's
comments...?
John
--
John W. Linville
linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org
next prev parent reply other threads:[~2007-09-16 2:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-15 13:22 Please pull 'adm8211' branch of wireless-2.6 John W. Linville
[not found] ` <20070915132220.GE6060-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-09-15 17:00 ` John W. Linville
[not found] ` <20070915170018.GC18930-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-09-15 18:25 ` David Miller
[not found] ` <20070915.112549.79067357.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2007-09-16 2:36 ` John W. Linville [this message]
[not found] ` <20070916023600.GA3967-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-09-16 3:26 ` Jeff Garzik
2007-09-15 21:32 ` Jeff Garzik
[not found] ` <46EC4F78.4050700-o2qLIJkoznsdnm+yROfE0A@public.gmane.org>
2007-09-16 0:16 ` Michael Wu
2007-09-16 0:56 ` Jeff Garzik
2007-09-16 4:47 ` Michael Wu
2007-09-16 4:50 ` David Miller
[not found] ` <20070915.215053.74746915.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2007-09-16 5:00 ` Michael Wu
[not found] ` <200709160047.45128.flamingice-R9e9/4HEdknk1uMJSBkQmQ@public.gmane.org>
2007-09-16 7:50 ` Jeff Garzik
2007-09-16 0:37 ` Michael Wu
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=20070916023600.GA3967@tuxdriver.com \
--to=linville-2xusbdqka4r54taoqtywwq@public.gmane.org \
--cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
--cc=flamingice-R9e9/4HEdknk1uMJSBkQmQ@public.gmane.org \
--cc=jeff-o2qLIJkoznsdnm+yROfE0A@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).