From: Larry Finger <Larry.Finger@lwfinger.net>
To: Christoph Egger <siccegge@stud.informatik.uni-erlangen.de>
Cc: linux-kernel@vger.kernel.org,
Stefano Brivio <stefano.brivio@polimi.it>,
linux-wireless@vger.kernel.org,
Reinhard.Tartler@informatik.uni-erlangen.de
Subject: Re: [PATCH] obsolete in kernel source (B43_LEGACY_RFKILL)
Date: Fri, 15 Jan 2010 11:12:11 -0600 [thread overview]
Message-ID: <4B50A1EB.2030903@lwfinger.net> (raw)
In-Reply-To: <20100113135937.GA5588@stud.informatik.uni-erlangen.de>
On 01/13/2010 07:59 AM, Christoph Egger wrote:
>
> Please keep me informed of this patch getting confirmed /
> merged so we can keep track of it.
The patch is in wireless-testing as commit
2f1f00fc9b477481ad5c63976385c345851fee3d. It will be in mainline kernel 2.6.34.
Larry
prev parent reply other threads:[~2010-01-15 17:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 13:59 [PATCH] obsolete in kernel source (B43_LEGACY_RFKILL) Christoph Egger
2010-01-15 17:12 ` Larry Finger [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=4B50A1EB.2030903@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=Reinhard.Tartler@informatik.uni-erlangen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=siccegge@stud.informatik.uni-erlangen.de \
--cc=stefano.brivio@polimi.it \
/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).