From: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: linux-pm@vger.kernel.org, "Rafael J. Wysocki" <rafael@kernel.org>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Ricardo Neri <ricardo.neri-calderon@linux.intel.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Jiri Pirko <jiri@resnulli.us>,
Johannes Berg <johannes@sipsolutions.net>,
Florian Westphal <fw@strlen.de>,
netdev@vger.kernel.org
Subject: Re: [PATCH v3 2/3] thermal: netlink: Add genetlink bind/unbind notifications
Date: Sat, 10 Feb 2024 11:50:52 +0100 [thread overview]
Message-ID: <ZcdVDEX5u982Qyes@linux.intel.com> (raw)
In-Reply-To: <20240209102858.51b06efc@kernel.org>
On Fri, Feb 09, 2024 at 10:28:58AM -0800, Jakub Kicinski wrote:
> On Fri, 9 Feb 2024 13:06:24 +0100 Stanislaw Gruszka wrote:
> > @@ -48,6 +64,15 @@ static inline int thermal_notify_tz_create(const struct thermal_zone_device *tz)
> > return 0;
> > }
> >
> > +int thermal_genl_register_notifier(struct notifier_block *nb)
> > +{
> > + return 0;
> > +}
> > +
> > +int thermal_genl_unregister_notifier(struct notifier_block *nb)
> > +{
> > + return 0;
> > +}
>
> static inline :)
Going to fix this in next respin.
Regards
Stanislaw
>
next prev parent reply other threads:[~2024-02-10 10:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 12:06 [PATCH v3 0/3] thermal/netlink/intel_hfi: Enable HFI feature only when required Stanislaw Gruszka
2024-02-09 12:06 ` [PATCH v3 1/3] genetlink: Add per family bind/unbind callbacks Stanislaw Gruszka
2024-02-09 12:06 ` [PATCH v3 2/3] thermal: netlink: Add genetlink bind/unbind notifications Stanislaw Gruszka
2024-02-09 18:28 ` Jakub Kicinski
2024-02-10 10:50 ` Stanislaw Gruszka [this message]
2024-02-09 12:06 ` [PATCH v3 3/3] thermal: intel: hfi: Enable interface only when required Stanislaw Gruszka
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=ZcdVDEX5u982Qyes@linux.intel.com \
--to=stanislaw.gruszka@linux.intel.com \
--cc=daniel.lezcano@linaro.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=jiri@resnulli.us \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rafael@kernel.org \
--cc=ricardo.neri-calderon@linux.intel.com \
--cc=srinivas.pandruvada@linux.intel.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).