From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Pavel Machek <pavel@ucw.cz>,
kernel@pengutronix.de, linux-leds@vger.kernel.org,
kernel-patch-test@lists.linaro.org,
Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Johannes Berg <johannes@sipsolutions.net>,
linux-bluetooth@vger.kernel.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 02/16] leds: triggers: let struct led_trigger::activate() return an error code
Date: Thu, 5 Jul 2018 23:31:28 +0200 [thread overview]
Message-ID: <1172a776-a951-28d5-fae4-824969f4a82b@gmail.com> (raw)
In-Reply-To: <20180702200535.1337-2-u.kleine-koenig@pengutronix.de>
Hi Uwe,
On 07/02/2018 10:05 PM, Uwe Kleine-König wrote:
> Given that activating a trigger can fail, let the callback return an
> indication. This prevents to have a trigger active according to the
> "trigger" sysfs attribute but not functional.
>
> All users are changed accordingly to return 0 for now. There is no intended
> change in behaviour.
>
> Acked-by: Pavel Machek <pavel@ucw.cz>
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
[...]
> -static void ieee80211_tx_led_activate(struct led_classdev *led_cdev)
> +static int ieee80211_tx_led_activate(struct led_classdev *led_cdev)
> {
> struct ieee80211_local *local = container_of(led_cdev->trigger,
> struct ieee80211_local,
> tx_led);
>
> atomic_inc(&local->tx_led_active);
> +
> + return 0
[...]
s/return 0/return 0;/
Fixed it up and applied. I'm taking lack of net maintainer feedback
as a tacit approval (or lack of interest).
--
Best regards,
Jacek Anaszewski
prev parent reply other threads:[~2018-07-05 21:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a9b3548b-09c4-fae4-1bce-abf3392b9ceb@gmail.com>
[not found] ` <a9b3548b-09c4-fae4-1bce-abf3392b9ceb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-07-02 20:05 ` [PATCH v7 02/16] leds: triggers: let struct led_trigger::activate() return an error code Uwe Kleine-König
2018-07-05 21:31 ` Jacek Anaszewski [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=1172a776-a951-28d5-fae4-824969f4a82b@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=davem@davemloft.net \
--cc=johan.hedberg@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=kernel-patch-test@lists.linaro.org \
--cc=kernel@pengutronix.de \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=pavel@ucw.cz \
--cc=u.kleine-koenig@pengutronix.de \
/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).