Re: linux-next: build failure after merge of the tty tree

[Greg KH]

On Tue, Jul 14, 2026 at 11:36:44AM +0530, Praveen Talari wrote:
> Hi Mark,
> 
> On 13-07-2026 20:12, Mark Brown wrote:
> > Hi all,
> > 
> > After merging the tty tree, today's linux-next build (x86_64 allmodconfig)
> > failed like this:
> > 
> > /tmp/next/build/drivers/tty/serial/qcom_geni_serial.c:1925:4: error:
> > cannot jump from this goto statement to its label
> >   1925 |                         goto error;
> >        |                         ^
> > /tmp/next/build/drivers/tty/serial/qcom_geni_serial.c:1931:44: note:
> > jump bypasses initialization of variable with __attribute__((cleanup))
> >   1931 |         PM_RUNTIME_ACQUIRE_IF_ENABLED(uport->dev, pm);
> >        |                                                   ^
> > /tmp/next/build/drivers/tty/serial/qcom_geni_serial.c:1916:3: error:
> > cannot jump from this goto statement to its label
> >   1916 |                 goto error;
> >        |                 ^
> > /tmp/next/build/drivers/tty/serial/qcom_geni_serial.c:1931:44: note:
> > jump bypasses initialization of variable with __attribute__((cleanup))
> >   1931 |         PM_RUNTIME_ACQUIRE_IF_ENABLED(uport->dev, pm);
> >        |                                                   ^
> > /tmp/next/build/drivers/tty/serial/qcom_geni_serial.c:1911:3: error:
> > cannot jump from this goto statement to its label
> >   1911 |                 goto error;
> >        |                 ^
> > /tmp/next/build/drivers/tty/serial/qcom_geni_serial.c:1931:44: note:
> > jump bypasses initialization of variable with __attribute__((cleanup))
> >   1931 |         PM_RUNTIME_ACQUIRE_IF_ENABLED(uport->dev, pm);
> >        |                                                   ^
> > /tmp/next/build/drivers/tty/serial/qcom_geni_serial.c:1887:3: error:
> > cannot jump from this goto statement to its label
> >   1887 |                 goto error;
> >        |                 ^
> > /tmp/next/build/drivers/tty/serial/qcom_geni_serial.c:1931:44: note:
> > jump bypasses initialization of variable with __attribute__((cleanup))
> >   1931 |         PM_RUNTIME_ACQUIRE_IF_ENABLED(uport->dev, pm);
> >        |                                                   ^
> > /tmp/next/build/drivers/tty/serial/qcom_geni_serial.c:1881:3: error:
> > cannot jump from this goto statement to its label
> >   1881 |                 goto error;
> >        |                 ^
> > /tmp/next/build/drivers/tty/serial/qcom_geni_serial.c:1931:44: note:
> > jump bypasses initialization of variable with __attribute__((cleanup))
> >   1931 |         PM_RUNTIME_ACQUIRE_IF_ENABLED(uport->dev, pm);
> >        |                                                   ^
> > /tmp/next/build/drivers/tty/serial/qcom_geni_serial.c:1872:4: error:
> > cannot jump from this goto statement to its label
> >   1872 |                         goto error;
> >        |                         ^
> > /tmp/next/build/drivers/tty/serial/qcom_geni_serial.c:1931:44: note:
> > jump bypasses initialization of variable with __attribute__((cleanup))
> >   1931 |         PM_RUNTIME_ACQUIRE_IF_ENABLED(uport->dev, pm);
> >        |                                                   ^
> > /tmp/next/build/drivers/tty/serial/qcom_geni_serial.c:1864:4: error:
> > cannot jump from this goto statement to its label
> >   1864 |                         goto error;
> >        |                         ^
> > /tmp/next/build/drivers/tty/serial/qcom_geni_serial.c:1931:44: note:
> > jump bypasses initialization of variable with __attribute__((cleanup))
> >   1931 |         PM_RUNTIME_ACQUIRE_IF_ENABLED(uport->dev, pm);
> >        |                                                   ^
> > /tmp/next/build/drivers/tty/serial/qcom_geni_serial.c:1848:3: error:
> > cannot jump from this goto statement to its label
> >   1848 |                 goto error;
> >        |                 ^
> > /tmp/next/build/drivers/tty/serial/qcom_geni_serial.c:1931:44: note:
> > jump bypasses initialization of variable with __attribute__((cleanup))
> >   1931 |         PM_RUNTIME_ACQUIRE_IF_ENABLED(uport->dev, pm);
> >        |                                                   ^
> > 8 errors generated.
> 
> I don't see these errors in my local build. Is there any specific way to
> build to see these errors?

Nope, I can't duplicate this either on my side just by building this
branch.  Is this coming from a change somewhere else that modifies
PM_RUNTIME_ACQUIRE_IF_ENABLED()?

thanks,

greg k-h