All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: pull request: wireless-2.6 2008-05-15
Date: Fri, 16 May 2008 09:21:57 -0400	[thread overview]
Message-ID: <20080516132157.GA3373@tuxdriver.com> (raw)
In-Reply-To: <20080515195341.GB25905@tuxdriver.com>

On Thu, May 15, 2008 at 03:53:41PM -0400, John W. Linville wrote:
> David,
> 
> Another quick round of fixes intended for 2.6.26...
> 
> Thanks!
> 
> John

Dave,

Please delay this pull if you haven't done it already!

John
-- 
John W. Linville
linville@tuxdriver.com

  reply	other threads:[~2008-05-16 13:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-15 19:53 pull request: wireless-2.6 2008-05-15 John W. Linville
2008-05-16 13:21 ` John W. Linville [this message]
2008-05-16 19:56   ` David Miller
2008-05-16 21:31 ` pull request: wireless-2.6 2008-05-16 John W. Linville
2008-05-16 21:31   ` John W. Linville
2008-05-19 23:32   ` David Miller
2008-05-19 23:32     ` David Miller

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=20080516132157.GA3373@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.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.