From: Johannes Berg <johannes@sipsolutions.net>
To: Borislav Petkov <bp@alien8.de>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-um@lists.infradead.org
Subject: Re: [PATCH v0 25/42] arch/um: Check notifier registration return value
Date: Mon, 08 Nov 2021 11:56:21 +0100 [thread overview]
Message-ID: <ce3a494b078ffca5df28475298ba6c491267da98.camel@sipsolutions.net> (raw)
In-Reply-To: <YYkAiFhxVsLaPTqr@zn.tnic>
On Mon, 2021-11-08 at 11:48 +0100, Borislav Petkov wrote:
> On Mon, Nov 08, 2021 at 11:23:59AM +0100, Johannes Berg wrote:
> > Maybe it should just return it? I don't see how this is ever possible,
> > since it's an initcall.
>
> If it would return it, you'd see the warning only when booting with
> "initcall_debug", I believe.
Oh, I thought we'd fail :)
> I can do that if it is preferred...
>
No strong opinion either way.
johannes
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next prev parent reply other threads:[~2021-11-08 10:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211108101157.15189-1-bp@alien8.de>
2021-11-08 10:11 ` [PATCH v0 25/42] arch/um: Check notifier registration return value Borislav Petkov
2021-11-08 10:23 ` Johannes Berg
2021-11-08 10:48 ` Borislav Petkov
2021-11-08 10:56 ` Johannes Berg [this message]
2021-11-08 10:11 ` [PATCH v0 42/42] notifier: Return an error when callback is already registered Borislav Petkov
2021-11-08 14:07 ` Geert Uytterhoeven
2021-11-08 14:21 ` Borislav Petkov
2021-11-08 15:25 ` Geert Uytterhoeven
2021-11-08 15:58 ` Borislav Petkov
2021-11-08 16:12 ` Geert Uytterhoeven
2021-11-08 16:21 ` Borislav Petkov
2021-11-08 20:59 ` Alan Stern
2021-11-08 21:18 ` Borislav Petkov
2021-11-08 10:19 ` [PATCH v0 00/42] notifiers: " Borislav Petkov
2021-11-08 14:17 ` Alan Stern
2021-11-08 14:24 ` Borislav Petkov
2021-11-08 14:35 ` Borislav Petkov
2021-11-08 16:23 ` Steven Rostedt
2021-11-08 16:29 ` Borislav Petkov
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=ce3a494b078ffca5df28475298ba6c491267da98.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
/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