From: Simon Horman <simon.horman@corigine.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Kalle Valo <kvalo@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
ath10k@lists.infradead.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH net-next 1/4] ath10k: Drop cleaning of driver data from probe error path and remove
Date: Thu, 1 Jun 2023 18:16:58 +0200 [thread overview]
Message-ID: <ZHjEehXjebG9pxuK@corigine.com> (raw)
In-Reply-To: <20230601082556.2738446-2-u.kleine-koenig@pengutronix.de>
On Thu, Jun 01, 2023 at 10:25:53AM +0200, Uwe Kleine-König wrote:
> The driver core cares for resetting driver data if probe fails and after
> remove. So drop the explicit and duplicate cleanup in the driver's
> functions.
>
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Reviewed-by: Simon Horman <simon.horman@corigine.com>
next prev parent reply other threads:[~2023-06-01 16:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 8:25 [PATCH net-next 0/4] Convert to platform remove callback returning void Uwe Kleine-König
2023-06-01 8:25 ` [PATCH net-next 1/4] ath10k: Drop cleaning of driver data from probe error path and remove Uwe Kleine-König
2023-06-01 16:16 ` Simon Horman [this message]
2023-06-09 12:28 ` Kalle Valo
2023-06-01 8:25 ` [PATCH net-next 2/4] ath10k: Drop checks that are always false Uwe Kleine-König
2023-06-01 16:16 ` Simon Horman
2023-06-01 8:25 ` [PATCH net-next 3/4] ath10k: Convert to platform remove callback returning void Uwe Kleine-König
2023-06-01 16:18 ` Simon Horman
2023-06-01 8:25 ` [PATCH net-next 4/4] atk10k: Don't opencode ath10k_pci_priv() in ath10k_ahb_priv() Uwe Kleine-König
2023-06-01 16:17 ` Simon Horman
2023-06-01 9:17 ` [PATCH net-next 0/4] Convert to platform remove callback returning void Kalle Valo
2023-06-01 9:30 ` Uwe Kleine-König
2023-06-01 10:44 ` 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=ZHjEehXjebG9pxuK@corigine.com \
--to=simon.horman@corigine.com \
--cc=ath10k@lists.infradead.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 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).