Re: [PATCH v0 00/42] notifiers: Return an error when callback is already registered
From: Steven Rostedt <rostedt@goodmis.org>
Date: 2021-11-08 16:23:26
Also in:
alsa-devel, intel-gfx, linux-alpha, linux-arm-kernel, linux-clk, linux-crypto, linux-edac, linux-fbdev, linux-hyperv, linux-iio, linux-leds, linux-mips, linux-pm, linux-remoteproc, linux-renesas-soc, linux-s390, linux-scsi, linux-sh, linux-staging, linux-tegra, linux-um, linux-usb, linuxppc-dev, lkml, rcu, sparclinux, xen-devel
On Mon, 8 Nov 2021 15:35:50 +0100 Borislav Petkov [off-list ref] wrote:
On Mon, Nov 08, 2021 at 03:24:39PM +0100, Borislav Petkov wrote:quoted
I guess I can add another indirection to notifier_chain_register() and avoid touching all the call sites.IOW, something like this below. This way I won't have to touch all the callsites and the registration routines would still return a proper value instead of returning 0 unconditionally.
I prefer this method. Question, how often does this warning trigger? Is it common to see in development? -- Steve