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 2010-10-07
Date: Fri, 08 Oct 2010 10:38:42 -0700 (PDT) [thread overview]
Message-ID: <20101008.103842.39184623.davem@davemloft.net> (raw)
In-Reply-To: <20101007185859.GD20950@tuxdriver.com>
From: "John W. Linville" <linville@tuxdriver.com>
Date: Thu, 7 Oct 2010 14:58:59 -0400
> Here are a few more more-or-less-one-liner fixes intended for 2.6.36.
> The one from Felix fixes a regression introduced in the 2.6.36 cycle.
> The one from Johannes fixes a crash reported by Ben Greear (as
> documented in the changelog). The one from me reverts and earlier patch
> from me that can result in stuff in dmesg from not calling
> netif_receive_skb in the proper context.
Pulled, thanks John.
prev parent reply other threads:[~2010-10-08 17:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 18:58 pull request: wireless-2.6 2010-10-07 John W. Linville
2010-10-08 17:38 ` 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=20101008.103842.39184623.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;
as well as URLs for NNTP newsgroup(s).