All of lore.kernel.org
 help / color / mirror / Atom feed
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/3] staging: r8188eu: start cleaning up led blinking
Date: Tue, 23 Aug 2022 20:49:56 +0200	[thread overview]
Message-ID: <91772e44-856d-cdee-e685-ff2ba4523c2e@gmail.com> (raw)
In-Reply-To: <20220822201329.95559-1-martin@kaiser.cx>

On 8/22/22 22:13, Martin Kaiser wrote:
> The code for led blinking contains too many states and state variables.
> This series is a first tiny step towards cleaning things up.
> 
> Martin Kaiser (3):
>    staging: r8188eu: don't restart "no link" blinking unnecessarily
>    staging: r8188eu: always cancel blink_work
>    staging: r8188eu: always update the status variables
> 
>   drivers/staging/r8188eu/core/rtw_led.c | 36 ++++++++++++--------------
>   1 file changed, 17 insertions(+), 19 deletions(-)
> 

Tested-by: Philipp Hortmann <philipp.g.hortmann@gmail.com> # Edimax N150

      parent reply	other threads:[~2022-08-23 18:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-22 20:13 [PATCH 0/3] staging: r8188eu: start cleaning up led blinking Martin Kaiser
2022-08-22 20:13 ` [PATCH 1/3] staging: r8188eu: don't restart "no link" blinking unnecessarily Martin Kaiser
2022-08-22 20:13 ` [PATCH 2/3] staging: r8188eu: always cancel blink_work Martin Kaiser
2022-08-22 20:13 ` [PATCH 3/3] staging: r8188eu: always update the status variables Martin Kaiser
2022-08-23 18:49 ` 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=91772e44-856d-cdee-e685-ff2ba4523c2e@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 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.