[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230209161606.79f064ae@kernel.org>
Date: Thu, 9 Feb 2023 16:16:06 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Kim Phillips <kim.phillips@....com>
Cc: Jiri Pirko <jiri@...nulli.us>, <netdev@...r.kernel.org>,
<davem@...emloft.net>, <pabeni@...hat.com>, <edumazet@...gle.com>,
<tariqt@...dia.com>, <saeedm@...dia.com>,
<jacob.e.keller@...el.com>, <gal@...dia.com>, <moshe@...dia.com>
Subject: Re: [patch net-next 0/7] devlink: params cleanups and
devl_param_driverinit_value_get() fix
On Thu, 9 Feb 2023 16:37:13 -0600 Kim Phillips wrote:
> On 2/9/23 3:31 PM, Jakub Kicinski wrote:
> > On Thu, 9 Feb 2023 15:05:46 -0600 Kim Phillips wrote:
> >> Is there a different tree the series can be rebased on, until net-next
> >> gets fixed?
> >
> > merge in net-next, the fix should be there but was merged a couple of
> > hours ago so probably not yet in linux-next
>
> I=Ok, I took next-20230209, git merged net-next/master, fixed a merge
> conflict to use the latter net-next/master version:
> ...and unfortunately still get a splat on that same Rome system:
Alright, so that's the splat I'm guessing the patch set was supposed
to address. Can you confirm that you're testing
next-20230209 + net-next/master + this patches from the list
? The previous crash (which I called "fixed in net-next") was an
unrelated bug in the socket layer. You still have to apply the
patches from the list to fix the devlink warning.
Powered by blists - more mailing lists