From: "John W. Linville" <linville@tuxdriver.com>
To: jeff@garzik.org
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: Please pull 'fixes-jgarzik' branch of wireless-2.6
Date: Thu, 10 Jan 2008 15:57:56 -0500 [thread overview]
Message-ID: <20080110205756.GG3109@tuxdriver.com> (raw)
In-Reply-To: <20080110194922.GF3109@tuxdriver.com>
On Thu, Jan 10, 2008 at 02:49:22PM -0500, John W. Linville wrote:
> Jeff,
>
> A couple more fixes for 2.6.24. The one from Mattias Nissler is already
> in your upstream tree...FYI.
>
> Let me know if there are problems!
Please disregard this request. The 'upstream-jgarzik-2' request is still valid.
Thanks,
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2008-01-10 21:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 19:49 Please pull 'fixes-jgarzik' branch of wireless-2.6 John W. Linville
2008-01-10 20:57 ` John W. Linville [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-01-16 21:27 John W. Linville
2008-01-18 19:40 ` Jeff Garzik
2008-01-08 5:15 John W. Linville
2008-01-08 6:04 ` David Miller
2007-12-20 15:54 John W. Linville
2007-12-16 4:31 John W. Linville
2007-12-17 19:34 ` John W. Linville
2007-12-17 20:07 ` David Miller
2007-12-17 20:18 ` Jeff Garzik
2007-12-17 21:10 ` Jeff Garzik
2007-11-30 3:29 John W. Linville
2007-12-01 21:20 ` Jeff Garzik
2007-11-06 20:07 John W. Linville
2007-11-07 19:13 ` John W. Linville
2007-11-07 19:24 ` Jeff Garzik
2007-10-26 3:08 John W. Linville
2007-10-29 9:48 ` Jeff Garzik
2007-10-18 22:09 John W. Linville
2007-10-20 3:04 ` Jeff Garzik
2007-10-03 1:20 John W. Linville
2007-10-03 17:39 ` Jeff Garzik
2007-08-06 20:14 John W. Linville
2007-08-07 21:25 ` 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=20080110205756.GG3109@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=jeff@garzik.org \
--cc=linux-wireless@vger.kernel.org \
--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 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.