Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Brian Norris <briannorris@chromium.org>
Cc: stable@vger.kernel.org
Subject: Re: Request to apply 6d3e0d8cc632 to stable kernels
Date: Tue, 18 Feb 2025 15:52:29 +0100	[thread overview]
Message-ID: <2025021822-stung-sitcom-f0c6@gregkh> (raw)
In-Reply-To: <Z6P-BnP_nZRz_H00@google.com>

On Wed, Feb 05, 2025 at 04:10:46PM -0800, Brian Norris wrote:
> Hi,
> 
> May I request this be ported to stable kernels?
> 
>   6d3e0d8cc632 ("kdb: Do not assume write() callback available")
> 
> It landed in v6.6, and I've tested the trivial cherry-pick to v6.1.y.
> AFAICT, it makes sense and applies cleanly to at least v5.15.y and
> v5.10.y (and possibly more), although I didn't test those.
> 
> It's a bit of an older (but trivial) fix, and I assume not many folks
> actually test out KDB/KGDB that often, but I wasted my time
> re-discovering it.

Now queued up,t hanks

greg k-h

      reply	other threads:[~2025-02-18 14:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-06  0:10 Request to apply 6d3e0d8cc632 to stable kernels Brian Norris
2025-02-18 14:52 ` Greg KH [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=2025021822-stung-sitcom-f0c6@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=briannorris@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox