Linux wireless drivers development
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: linville@tuxdriver.com
Cc: proski@gnu.org, linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: pull request: wireless-next-2.6 2009-12-24
Date: Fri, 25 Dec 2009 17:10:29 -0800 (PST)	[thread overview]
Message-ID: <20091225.171029.193718771.davem@davemloft.net> (raw)
In-Reply-To: <20091225163801.GA4481@tuxdriver.com>

From: "John W. Linville" <linville@tuxdriver.com>
Date: Fri, 25 Dec 2009 11:38:01 -0500

> Perhaps, but not intentionally.  Hopefully the patch I posted is
> sufficient to get things working for non-gawk users...?

It worked here, so I applied it on top
of your pull request and pushed back out
to net-next-2.6

Thanks!

      reply	other threads:[~2009-12-26  1:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-24 20:47 pull request: wireless-next-2.6 2009-12-24 John W. Linville
2009-12-24 21:53 ` David Miller
2009-12-25  4:47   ` John W. Linville
2009-12-25  5:51     ` Pavel Roskin
2009-12-25 16:38       ` John W. Linville
2009-12-26  1:10         ` David Miller [this message]

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=20091225.171029.193718771.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.org \
    --cc=proski@gnu.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