[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <72a4d07d-3ac8-4c39-8501-b3f93a26654a@paulmck-laptop>
Date: Thu, 30 May 2024 13:40:54 -0700
From: "Paul E. McKenney" <paulmck@...nel.org>
To: Thierry Reding <thierry.reding@...il.com>
Cc: Abhinav Kumar <quic_abhinavk@...cinc.com>, sfr@...b.auug.org.au,
Rob Clark <robdclark@...il.com>,
Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
Sean Paul <sean@...rly.run>,
Marijn Suijten <marijn.suijten@...ainline.org>,
David Airlie <airlied@...il.com>, Daniel Vetter <daniel@...ll.ch>,
Jon Hunter <jonathanh@...dia.com>, linux-arm-msm@...r.kernel.org,
dri-devel@...ts.freedesktop.org, freedreno@...ts.freedesktop.org,
linux-kernel@...r.kernel.org
Subject: Re: [BUG] Build failure and alleged fix for next-20240523
On Thu, May 30, 2024 at 08:28:17PM +0200, Thierry Reding wrote:
> On Thu May 30, 2024 at 6:55 PM CEST, Paul E. McKenney wrote:
> > On Fri, May 24, 2024 at 12:57:58PM -0700, Abhinav Kumar wrote:
> > > Hello
> > >
> > > On 5/24/2024 12:55 PM, Paul E. McKenney wrote:
> > > > Hello!
> > > >
> > > > I get the following allmodconfig build error on x86 in next-20240523:
> > > >
> > > > Traceback (most recent call last):
> > > > File "drivers/gpu/drm/msm/registers/gen_header.py", line 970, in <module>
> > > > main()
> > > > File "drivers/gpu/drm/msm/registers/gen_header.py", line 951, in main
> > > > parser.add_argument('--validate', action=argparse.BooleanOptionalAction)
> > > > AttributeError: module 'argparse' has no attribute 'BooleanOptionalAction'
> > > >
> > > > The following patch allows the build to complete successfully:
> > > >
> > > > https://patchwork.kernel.org/project/dri-devel/patch/20240508091751.336654-1-jonathanh@nvidia.com/#25842751
> > > >
> > > > As to whether this is a proper fix, I must defer to the DRM folks on CC.
> > >
> > > Thanks for the report.
> > >
> > > I have raised a merge request for
> > > https://patchwork.freedesktop.org/patch/593057/ to make it available for the
> > > next fixes release for msm.
> >
> > Thank you!
> >
> > This still is not in -next, so I am putting it into -rcu just to silence
> > the diagnostic. Or should I push this to mainline via -rcu?
>
> I pushed this to drm-misc-fixes earlier today, so should show up in
> linux-next soon and hopefully in v6.10-rc2.
Thank you, Thierry!
Thanx, Paul
Powered by blists - more mailing lists