From: David Miller <davem@davemloft.net>
To: linville@tuxdriver.com
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: pull request: wireless-2.6 2009-02-23
Date: Tue, 24 Feb 2009 23:53:17 -0800 (PST) [thread overview]
Message-ID: <20090224.235317.10940015.davem@davemloft.net> (raw)
In-Reply-To: <20090223192617.GA3553@tuxdriver.com>
From: "John W. Linville" <linville@tuxdriver.com>
Date: Mon, 23 Feb 2009 14:26:17 -0500
> Here are a couple of fixes, one for an oops and one for a warning. Also
> included is a PCI ID addition. These are intended for 2.6.29.
Pulled, thanks John.
> P.S. This causes some conflicts with -next. The ath9k conflict is
> simple. The orinoco conflict involves moving some code from orinoco.c
> to orinoco/main.c in -next (where orinoco.c no longer exists). I have
> included a "merge-test" branch in the wireless-next-2.6 tree to provide
> and example for the merge when you get to it.
Ok, I'll take care of that now, thanks John.
prev parent reply other threads:[~2009-02-25 7:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 19:26 John W. Linville
2009-02-25 7:53 ` 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=20090224.235317.10940015.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®