Netdev List
 help / color / mirror / Atom feed
From: Jeremy Kerr <jk@codeconstruct.com.au>
To: Minhong He <heminhong@kylinos.cn>, netdev@vger.kernel.org
Cc: Matt Johnston <matt@codeconstruct.com.au>
Subject: Re: [PATCH] mctp: check register_netdevice_notifier() error in mctp_device_init()
Date: Wed, 15 Jul 2026 08:37:22 +0800	[thread overview]
Message-ID: <20d74693ac673ba1db0c0052a7236db777fc5ec5.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20260713073918.419422-1-heminhong@kylinos.cn>

Hi,

> [PATCH] mctp: check register_netdevice_notifier() error in mctp_device_init()

Please include the target tree in the subject prefix. SInce this is for
the net tree, you want something like:

  [PATCH net] mctp: check ...

> mctp_device_init() handles errors from rtnl_af_register() and
> rtnl_register_many(), but ignores the return value of
> register_netdevice_notifier(). If notifier registration fails, init
> can still return success while the module is only partially initialized.
> 
> Check the notifier registration error and fail module init early.

The change itself looks good, thanks.

> Fixes: d51705614f66 ("mctp: Handle error of rtnl_register_module().")

... but no newline between the fixes and signed-off-by (and other tags).

Also, make sure you CC all the necessary maintainers; you're getting a
nipa CI failure due to that.

With those addressed:

Acked-by: Jeremy Kerr <jk@codeconstruct.com.au>

Cheers,


Jeremy

  reply	other threads:[~2026-07-15  0:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-13  7:39 [PATCH] mctp: check register_netdevice_notifier() error in mctp_device_init() Minhong He
2026-07-15  0:37 ` Jeremy Kerr [this message]
2026-07-16  6:35   ` [PATCH net v2] " Minhong He
2026-07-16  7:32     ` Kuniyuki Iwashima
2026-07-16  7:53       ` Jeremy Kerr

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=20d74693ac673ba1db0c0052a7236db777fc5ec5.camel@codeconstruct.com.au \
    --to=jk@codeconstruct.com.au \
    --cc=heminhong@kylinos.cn \
    --cc=matt@codeconstruct.com.au \
    --cc=netdev@vger.kernel.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