mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Thompson <daniel.thompson@linaro.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jason Wessel <jason.wessel@windriver.com>,
	linux-kernel@vger.kernel.org,
	Douglas Anderson <dianders@chromium.org>,
	Yuran Pereira <yuran.pereira@hotmail.com>
Subject: [GIT PULL] kgdb changes for v6.7
Date: Mon, 6 Nov 2023 17:28:48 +0000	[thread overview]
Message-ID: <20231106172848.GA27605@aspen.lan> (raw)

The following changes since commit 94f6f0550c625fab1f373bb86a6669b45e9748b3:

  Linux 6.6-rc5 (2023-10-08 13:49:43 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/danielt/linux.git/ tags/kgdb-6.7-rc1

for you to fetch changes up to 23816724fdbd47c28bc998866fd7bc5ad9f0e535:

  kdb: Corrects comment for kdballocenv (2023-11-06 17:13:55 +0000)

----------------------------------------------------------------
kgdb patches for 6.7

Just two patches for you this time!

 * During a panic, flush the console before entering kgdb. This makes
   things a little easier to comprehend, especially if an NMI backtrace
   was triggered on all CPUs just before we enter the panic routines.
 * Correcting a couple of misleading (a.k.a. plain wrong) comments.

Signed-off-by: Daniel Thompson <daniel.thompson@linaro.org>

----------------------------------------------------------------
Douglas Anderson (1):
      kgdb: Flush console before entering kgdb on panic

Yuran Pereira (1):
      kdb: Corrects comment for kdballocenv

 kernel/debug/debug_core.c   | 3 +++
 kernel/debug/kdb/kdb_main.c | 7 +++----
 2 files changed, 6 insertions(+), 4 deletions(-)

             reply	other threads:[~2023-11-06 17:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-06 17:28 Daniel Thompson [this message]
2023-11-08 17:52 ` pr-tracker-bot

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=20231106172848.GA27605@aspen.lan \
    --to=daniel.thompson@linaro.org \
    --cc=dianders@chromium.org \
    --cc=jason.wessel@windriver.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=yuran.pereira@hotmail.com \
    /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

all inboxes | Powered by JetHome®