From: Michael Buesch <mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
To: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org,
Larry Finger
<Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
Subject: Re: [PATCH] bcm43xx-d80211: Interrogate hardware-enable switch and update LEDs
Date: Fri, 26 Jan 2007 10:01:20 +0100 [thread overview]
Message-ID: <200701261001.20677.mb@bu3sch.de> (raw)
In-Reply-To: <20070126024451.GK10282-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
On Friday 26 January 2007 03:44, John W. Linville wrote:
> On Sat, Dec 30, 2006 at 11:25:15PM -0600, Larry Finger wrote:
> > The current bcm43xx driver ignores any wireless-enable switches on mini-PCI
> > and mini-PCI-E cards. This patch implements a new routine to interrogate the
> > radio hardware enabled bit in the interface, logs the initial state and any
> > changes in the switch (if debugging enabled), activates the LED to show the
> > state, and changes the periodic work handler to provide 1 second response
> > to switch changes and to account for changes in the periodic work specs. It
> > also incorporates changes in the LED state that were accepted into mainline
> > some time ago.
>
> Larry,
>
> I wanted to merge this, but a slew of changes pulled from Michael
> makes this patch fail to apply.
Hm? What did you pull?
--
Greetings Michael.
prev parent reply other threads:[~2007-01-26 9:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-31 5:25 [PATCH] bcm43xx-d80211: Interrogate hardware-enable switch and update LEDs Larry Finger
[not found] ` <459749bb.q8/+AsgXLhurTs3u%Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2006-12-31 12:03 ` Michael Buesch
2007-01-26 2:44 ` John W. Linville
[not found] ` <20070126024451.GK10282-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-01-26 9:01 ` Michael Buesch [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=200701261001.20677.mb@bu3sch.de \
--to=mb-fseuscv1ubazqb+pc5nmwq@public.gmane.org \
--cc=Bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org \
--cc=Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org \
--cc=linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.