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, sfr@canb.auug.org.au
Subject: Re: pull request: wireless-2.6 2009-03-16
Date: Tue, 17 Mar 2009 14:39:49 -0700 (PDT) [thread overview]
Message-ID: <20090317.143949.250643299.davem@davemloft.net> (raw)
In-Reply-To: <20090316231423.GA3633@tuxdriver.com>
From: "John W. Linville" <linville@tuxdriver.com>
Date: Mon, 16 Mar 2009 19:14:24 -0400
> Here is a group of patches intended for 2.6.29. The one from me is
> minor, but it cuts-down on log SPAM for ipw2100, ipw2200, and hostap
> users. The two from Jouni fix some panics he observed himself.
>
> The first one from Luis fixes bug 12110 at bugzilla.kernel.org. I know
> he has worked on it for a long time and I've had several desperate users
> asking for it, so it must be good. :-) Unfortunately, it causes some
> nasty merge errors with what is in net-next-2.6 and wireless-next-2.6.
> I created a merge-test branch in wireless-next-2.6, and the merge commit
> log goes into more detail about resolving the issue. In short, you
> probably want to diff drivers/net/ath9k against the merge-test branch...
>
> Please let me know if there are problems!
Pulled, thanks John.
Wish me luck with the net-next-2.6 merge :-)
prev parent reply other threads:[~2009-03-17 21:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 23:14 pull request: wireless-2.6 2009-03-16 John W. Linville
[not found] ` <20090316231423.GA3633-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2009-03-17 2:00 ` Stephen Rothwell
2009-03-17 21:39 ` 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=20090317.143949.250643299.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 \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).