From: Jakub Kicinski <kuba@kernel.org>
To: Jiri Pirko <jiri@resnulli.us>
Cc: kernel test robot <lkp@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
netdev@vger.kernel.org, Ido Schimmel <idosch@idosch.org>
Subject: Re: [linux-next:master] BUILD REGRESSION e7d6987e09a328d4a949701db40ef63fbb970670
Date: Tue, 26 Apr 2022 10:35:37 -0700 [thread overview]
Message-ID: <20220426103537.4d0f43b7@kernel.org> (raw)
In-Reply-To: <YmgIu4L6f4WfrIte@nanopsycho>
On Tue, 26 Apr 2022 16:59:07 +0200 Jiri Pirko wrote:
> >>is this one on your radar?
> >
> >Will send a fix for this, thanks.
>
> Can't find the line. I don't see
> e7d6987e09a328d4a949701db40ef63fbb970670 in linux-next :/
Eh, no idea which tree it came from, but FWIW I do have that one in my
local tree. So here it is:
844 devlink_linecard = devlink_linecard_create(priv_to_devlink(mlxsw_core),
845 slot_index, &mlxsw_linecard_ops,
846 linecard);
847 if (IS_ERR(devlink_linecard)) {
848 err = PTR_ERR(devlink_linecard);
849 goto err_devlink_linecard_create;
850 }
851 linecard->devlink_linecard = devlink_linecard;
852 INIT_DELAYED_WORK(&linecard->status_event_to_dw,
853 &mlxsw_linecard_status_event_to_work);
Unless I'm missing something looks like a false positive :S
next prev parent reply other threads:[~2022-04-26 17:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 5:42 [linux-next:master] BUILD REGRESSION e7d6987e09a328d4a949701db40ef63fbb970670 kernel test robot
2022-04-26 12:17 ` Jakub Kicinski
2022-04-26 12:41 ` Jiri Pirko
2022-04-26 14:59 ` Jiri Pirko
2022-04-26 17:35 ` Jakub Kicinski [this message]
2022-04-27 6:45 ` Jiri Pirko
2022-04-28 11:37 ` Chen, Rong A
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=20220426103537.4d0f43b7@kernel.org \
--to=kuba@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=idosch@idosch.org \
--cc=jiri@resnulli.us \
--cc=lkp@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).