From: Florian Fainelli <f.fainelli@gmail.com>
To: bcm-kernel-feedback-list@broadcom.com,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Ray Jui" <rjui@broadcom.com>,
"Scott Branden" <sbranden@broadcom.com>
Cc: linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH 1/3] soc: bcm: bcm2835-power: Drop empty platform remove function
Date: Mon, 12 Dec 2022 14:56:14 -0800 [thread overview]
Message-ID: <20221212225614.1647812-1-f.fainelli@gmail.com> (raw)
In-Reply-To: <20221212222549.3779846-2-u.kleine-koenig@pengutronix.de>
On Mon, 12 Dec 2022 23:25:47 +0100, Uwe Kleine-König <u.kleine-koenig@pengutronix.de> wrote:
> A remove callback just returning 0 is equivalent to no remove callback
> at all. So drop the useless function.
>
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> ---
Applied to https://github.com/Broadcom/stblinux/commits/drivers/next, thanks!
--
Florian
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Florian Fainelli <f.fainelli@gmail.com>
To: bcm-kernel-feedback-list@broadcom.com,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Ray Jui" <rjui@broadcom.com>,
"Scott Branden" <sbranden@broadcom.com>
Cc: linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH 1/3] soc: bcm: bcm2835-power: Drop empty platform remove function
Date: Mon, 12 Dec 2022 14:56:14 -0800 [thread overview]
Message-ID: <20221212225614.1647812-1-f.fainelli@gmail.com> (raw)
In-Reply-To: <20221212222549.3779846-2-u.kleine-koenig@pengutronix.de>
On Mon, 12 Dec 2022 23:25:47 +0100, Uwe Kleine-König <u.kleine-koenig@pengutronix.de> wrote:
> A remove callback just returning 0 is equivalent to no remove callback
> at all. So drop the useless function.
>
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> ---
Applied to https://github.com/Broadcom/stblinux/commits/drivers/next, thanks!
--
Florian
next prev parent reply other threads:[~2022-12-12 22:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 22:25 [PATCH 0/3] soc: Drop empty platform remove function Uwe Kleine-König
2022-12-12 22:25 ` Uwe Kleine-König
2022-12-12 22:25 ` [PATCH 1/3] soc: bcm: bcm2835-power: " Uwe Kleine-König
2022-12-12 22:25 ` Uwe Kleine-König
2022-12-12 22:56 ` Florian Fainelli [this message]
2022-12-12 22:56 ` Florian Fainelli
2022-12-12 22:25 ` [PATCH 2/3] soc: mediatek: mutex: " Uwe Kleine-König
2022-12-12 22:25 ` Uwe Kleine-König
2022-12-12 22:25 ` Uwe Kleine-König
2022-12-13 9:50 ` AngeloGioacchino Del Regno
2022-12-13 9:50 ` AngeloGioacchino Del Regno
2022-12-16 12:27 ` Matthias Brugger
2022-12-16 12:27 ` Matthias Brugger
2022-12-12 22:25 ` [PATCH 3/3] soc: tegra: cbb: " Uwe Kleine-König
2023-01-12 21:55 ` Uwe Kleine-König
2023-02-15 7:47 ` Uwe Kleine-König
2023-02-15 9:47 ` Sumit Gupta
2023-04-05 12:41 ` (subset) " Thierry Reding
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=20221212225614.1647812-1-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--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 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.