All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Sasha Levin <sashal@kernel.org>,
	stable@vger.kernel.org, llvm@lists.linux.dev,
	Masahiro Yamada <masahiroy@kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>
Subject: Re: Apply 0a6de78cff60 to 5.15+
Date: Tue, 18 Oct 2022 08:48:12 +0200	[thread overview]
Message-ID: <Y05MLG3EFoOuYmi1@kroah.com> (raw)
In-Reply-To: <Y02WW7iIeWPFTV8L@dev-arch.thelio-3990X>

On Mon, Oct 17, 2022 at 10:52:27AM -0700, Nathan Chancellor wrote:
> Hi Greg and Sasha,
> 
> Please consider applying the following commits to 5.19 and 6.0:
> 
> 4f001a21080f ("Kconfig.debug: simplify the dependency of DEBUG_INFO_DWARF4/5")
> bb1435f3f575 ("Kconfig.debug: add toolchain checks for DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT")
> 0a6de78cff60 ("lib/Kconfig.debug: Add check for non-constant .{s,u}leb128 support to DWARF5")
> 
> The main change is the final one but the second patch is a prerequisite
> and a useful fix in its own right. The first change allows the second to
> apply cleanly and it is a good clean up as well.
> 
> I have verified that they apply cleanly to those trees with 'patch -p1'.
> Attached is a manual backport for 5.15; the changes should not be
> necessary for older trees, as they do not have support for DWARF 5.
> 
> If there are any problems or questions, please let me know.

All now queued up, thanks.

greg k-h

      reply	other threads:[~2022-10-18  6:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-17 17:52 Apply 0a6de78cff60 to 5.15+ Nathan Chancellor
2022-10-18  6:48 ` Greg Kroah-Hartman [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=Y05MLG3EFoOuYmi1@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=llvm@lists.linux.dev \
    --cc=masahiroy@kernel.org \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=sashal@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.