From: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
To: Jeff Garzik <jeff-o2qLIJkoznsdnm+yROfE0A@public.gmane.org>
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org
Subject: Re: Please pull 'bcm43xx' branch of wireless-2.6?
Date: Mon, 31 Jul 2006 16:04:56 -0400 [thread overview]
Message-ID: <20060731200450.GF10138@tuxdriver.com> (raw)
In-Reply-To: <44CE61A7.4010207-o2qLIJkoznsdnm+yROfE0A@public.gmane.org>
On Mon, Jul 31, 2006 at 04:01:43PM -0400, Jeff Garzik wrote:
> John W. Linville wrote:
> >Jeff, if a 10ms maximum delay is still acceptable to you, then please
> >pull from the bcm43xx branch of wireless-2.6 into the upstream branch
> >of netdev-2.6.
>
> Just to be clear, 'upstream' not 'upstream-fixes', correct?
Yes, queued for 2.6.19.
Thanks,
John
--
John W. Linville
linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org
next prev parent reply other threads:[~2006-07-31 20:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 0:22 Please pull 'upstream-fixes' branch of wireless-2.6 John W. Linville
2006-07-28 0:23 ` Please pull 'upstream' " John W. Linville
[not found] ` <20060728002358.GB11621-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2006-07-28 0:37 ` What's new in 'bcm43xx' branch of wireless-2.6? John W. Linville
[not found] ` <20060728003753.GC11621-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2006-07-31 19:10 ` Please pull " John W. Linville
2006-07-31 20:01 ` Jeff Garzik
[not found] ` <44CE61A7.4010207-o2qLIJkoznsdnm+yROfE0A@public.gmane.org>
2006-07-31 20:04 ` John W. Linville [this message]
2006-08-03 21:21 ` Jeff Garzik
2006-07-29 4:33 ` Please pull 'upstream' branch of wireless-2.6 Jeff Garzik
2006-07-29 4:32 ` Please pull 'upstream-fixes' " Jeff Garzik
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=20060731200450.GF10138@tuxdriver.com \
--to=linville-2xusbdqka4r54taoqtywwq@public.gmane.org \
--cc=Bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org \
--cc=jeff-o2qLIJkoznsdnm+yROfE0A@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 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.