From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Martin Kaiser <martin@kaiser.cx>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Phillip Potter <phil@philpotter.co.uk>,
Michael Straube <straube.linux@gmail.com>,
Pavel Skripkin <paskripkin@gmail.com>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] staging: r8188eu: drop some stop/removed checks in the led layer
Date: Sun, 25 Sep 2022 23:05:52 +0200 [thread overview]
Message-ID: <c6677024-0c7f-65c6-f7d0-5916840c9a4f@gmail.com> (raw)
In-Reply-To: <20220925140406.112991-1-martin@kaiser.cx>
On 9/25/22 16:04, Martin Kaiser wrote:
> Here's two small patches that remove unnecessary checks of
> bSurpriseRemoved and bDriverStopped in the led layer.
>
> Martin Kaiser (2):
> staging: r8188eu: don't check bSurpriseRemoved in SwLedOff
> staging: r8188eu: don't check for stop/removal in the blink worker
>
> drivers/staging/r8188eu/core/rtw_led.c | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
Quick download test is working.
Observed LED is working fine
Tested-by: Philipp Hortmann <philipp.g.hortmann@gmail.com> # Edimax N150
prev parent reply other threads:[~2022-09-25 21:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 14:04 [PATCH 0/2] staging: r8188eu: drop some stop/removed checks in the led layer Martin Kaiser
2022-09-25 14:04 ` [PATCH 1/2] staging: r8188eu: don't check bSurpriseRemoved in SwLedOff Martin Kaiser
2022-09-25 14:04 ` [PATCH 2/2] staging: r8188eu: don't check for stop/removal in the blink worker Martin Kaiser
2022-09-25 21:05 ` Philipp Hortmann [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=c6677024-0c7f-65c6-f7d0-5916840c9a4f@gmail.com \
--to=philipp.g.hortmann@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=martin@kaiser.cx \
--cc=paskripkin@gmail.com \
--cc=phil@philpotter.co.uk \
--cc=straube.linux@gmail.com \
/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).