From: Jakub Kicinski <kuba@kernel.org>
To: Alexandru Tachici <alexandru.tachici@analog.com>
Cc: <linux-kernel@vger.kernel.org>, <andrew@lunn.ch>,
<linux@armlinux.org.uk>, <davem@davemloft.net>,
<edumazet@google.com>, <pabeni@redhat.com>,
<netdev@vger.kernel.org>, <lennart@lfdomain.com>
Subject: Re: [net v3 1/1] net: ethernet: adi: adin1110: Fix notifiers
Date: Wed, 26 Oct 2022 20:40:17 -0700 [thread overview]
Message-ID: <20221026204017.0a0afff5@kernel.org> (raw)
In-Reply-To: <20221025075227.9276-2-alexandru.tachici@analog.com>
On Tue, 25 Oct 2022 10:52:27 +0300 Alexandru Tachici wrote:
> + int err;
> +
> + err = adin1110_setup_notifiers();
> + if (err)
> + return err;
> +
> + return spi_register_driver(&adin1110_driver);
What unregisters the notifies if spi_register_driver()
fails, now?
prev parent reply other threads:[~2022-10-27 3:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 7:52 [net v3 0/1] net: ethernet: adi: adin1110: Fix notifiers Alexandru Tachici
2022-10-25 7:52 ` [net v3 1/1] " Alexandru Tachici
2022-10-27 3:40 ` Jakub Kicinski [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=20221026204017.0a0afff5@kernel.org \
--to=kuba@kernel.org \
--cc=alexandru.tachici@analog.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=lennart@lfdomain.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).