public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Martin Kaiser <martin@kaiser.cx>
Cc: stable@vger.kernel.org, Nick Desaulniers <ndesaulniers@google.com>
Subject: Re: backport 790756c7e022 to 4.14 and 4.19?
Date: Mon, 30 Oct 2023 19:15:16 -0400	[thread overview]
Message-ID: <ZUA5BDnos1ASlFqM@sashalap> (raw)
In-Reply-To: <20231030212510.equbu7lxlslgoy3t@viti.kaiser.cx>

On Mon, Oct 30, 2023 at 10:25:10PM +0100, Martin Kaiser wrote:
>Dear all,
>
>after upgrading my toolchain to gcc 13.2 and GNU assembler (GNU
>Binutils) 2.41.0.20230926, compiling a 4.14 kernel fails
>
>arch/arm/mm/proc-arm926.S: Assembler messages:
>arch/arm/mm/proc-arm926.S:477: Error: junk at end of line, first
>unrecognized character is `#'
>
>The problem is that gas 2.41.0.20230926 does no longer support
>Solaris style section attributes like
>.section ".start", #alloc, #execinstr
>
>Commit 790756c7e022 ("ARM: 8933/1: replace Sun/Solaris style flag on
>section directive") fixed up the section attributes that used the legacy
>syntax. It seems that this commit landed in 5.5 and has already been
>backported to 5.4.
>
>Should we backport this commit to 4.19 and 4.14 as well? If so, should I
>submit patches that apply against the 4.19 and 4.14 trees or do you want
>to resolve the conflicts when you queue up the patch?

I'll queue it up, thanks!

-- 
Thanks,
Sasha

      reply	other threads:[~2023-10-30 23:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-30 21:25 backport 790756c7e022 to 4.14 and 4.19? Martin Kaiser
2023-10-30 23:15 ` Sasha Levin [this message]

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=ZUA5BDnos1ASlFqM@sashalap \
    --to=sashal@kernel.org \
    --cc=martin@kaiser.cx \
    --cc=ndesaulniers@google.com \
    --cc=stable@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