The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Thierry Reding" <thierry.reding@gmail.com>
To: <paulmck@kernel.org>, "Abhinav Kumar" <quic_abhinavk@quicinc.com>
Cc: <sfr@canb.auug.org.au>, "Rob Clark" <robdclark@gmail.com>,
	"Dmitry Baryshkov" <dmitry.baryshkov@linaro.org>,
	"Sean Paul" <sean@poorly.run>,
	"Marijn Suijten" <marijn.suijten@somainline.org>,
	"David Airlie" <airlied@gmail.com>,
	"Daniel Vetter" <daniel@ffwll.ch>,
	"Jon Hunter" <jonathanh@nvidia.com>,
	<linux-arm-msm@vger.kernel.org>,
	<dri-devel@lists.freedesktop.org>,
	<freedreno@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] Build failure and alleged fix for next-20240523
Date: Thu, 30 May 2024 20:28:17 +0200	[thread overview]
Message-ID: <D1N6WYWR463J.3UVC2PP2CUIY4@gmail.com> (raw)
In-Reply-To: <4f821c7f-6201-470f-b39d-ba689ca027d9@paulmck-laptop>

[-- Attachment #1: Type: text/plain, Size: 1478 bytes --]

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.

Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-05-30 18:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-24 19:55 [BUG] Build failure and alleged fix for next-20240523 Paul E. McKenney
2024-05-24 19:57 ` Abhinav Kumar
2024-05-24 21:11   ` Jon Hunter
2024-05-30 16:55   ` Paul E. McKenney
2024-05-30 18:28     ` Thierry Reding [this message]
2024-05-30 20:40       ` Paul E. McKenney

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=D1N6WYWR463J.3UVC2PP2CUIY4@gmail.com \
    --to=thierry.reding@gmail.com \
    --cc=airlied@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marijn.suijten@somainline.org \
    --cc=paulmck@kernel.org \
    --cc=quic_abhinavk@quicinc.com \
    --cc=robdclark@gmail.com \
    --cc=sean@poorly.run \
    --cc=sfr@canb.auug.org.au \
    /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