From: Kalle Valo <kvalo@codeaurora.org>
To: Lucas Stach <dev@lynxeye.de>
Cc: Michael Buesch <m@bues.ch>,
linux-wireless@vger.kernel.org, b43-dev@lists.infradead.org
Subject: Re: b43: only hardcode LED behavior if SPROM doesn't encode any
Date: Thu, 16 Jun 2016 15:15:05 +0000 (UTC) [thread overview]
Message-ID: <20160616151505.C0EBD613FD@smtp.codeaurora.org> (raw)
In-Reply-To: <1464987843-6928-1-git-send-email-dev@lynxeye.de>
Lucas Stach <dev@lynxeye.de> wrote:
> Only hardcode the LED behavior if the SROM doesn't provide any for all
> LEDs of the card. This avoids instantiating LED triggers for unconnected
> LEDs, while (hopefully) keeping things working for old cards with a
> blank SROM.
>
> Signed-off-by: Lucas Stach <dev@lynxeye.de>
Thanks, 1 patch applied to wireless-drivers-next.git:
508f1222ba4e b43: only hardcode LED behavior if SPROM doesn't encode any
--
Sent by pwcli
https://patchwork.kernel.org/patch/9154077/
next prev parent reply other threads:[~2016-06-16 15:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 21:04 [PATCH] b43: only hardcode LED behavior if SPROM doesn't encode any Lucas Stach
2016-06-03 21:09 ` Michael Büsch
2016-06-03 21:09 ` Michael Büsch
2016-06-16 15:15 ` Kalle Valo [this message]
2016-06-16 15:15 ` Kalle Valo
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=20160616151505.C0EBD613FD@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=b43-dev@lists.infradead.org \
--cc=dev@lynxeye.de \
--cc=linux-wireless@vger.kernel.org \
--cc=m@bues.ch \
/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.