linux-kernel.vger.kernel.org archive mirror
 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, Chuhong Yuan <hslester96@gmail.com>,
	Nadav Amit <namit@vmware.com>
Subject: [GIT PULL] kgdb changes v5.4-rc1
Date: Thu, 19 Sep 2019 16:59:46 +0100	[thread overview]
Message-ID: <20190919155946.htzamn3s3ovw7ujh@holly.lan> (raw)

The following changes since commit d1abaeb3be7b5fa6d7a1fbbd2e14e3310005c4c1:

  Linux 5.3-rc5 (2019-08-18 14:31:08 -0700)

are available in the Git repository at:

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

for you to fetch changes up to d8a050f5a3e8242242df6430d5980c142350e461:

  kgdb: fix comment regarding static function (2019-09-03 11:19:41 +0100)

----------------------------------------------------------------
kgdb patches for 5.4-rc1

It has been a quiet dev cycle for kgdb. There has been some good stuff
for kdb on the mailing list but unfortunately the patches caused a
couple of problems with the kdb pager so I had to drop those and they
will have to wait for next time!

That just leaves us with just a couple of very tiny clean ups for now:

 * Fix a broken comment
 * Use str_has_prefix() for the grep "pipe" in kdb

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

----------------------------------------------------------------
Chuhong Yuan (1):
      kdb: Replace strncmp with str_has_prefix

Nadav Amit (1):
      kgdb: fix comment regarding static function

 kernel/debug/debug_core.c   | 5 +----
 kernel/debug/kdb/kdb_main.c | 2 +-
 2 files changed, 2 insertions(+), 5 deletions(-)

             reply	other threads:[~2019-09-19 15:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-19 15:59 Daniel Thompson [this message]
2019-09-20 19:10 ` [GIT PULL] kgdb changes v5.4-rc1 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=20190919155946.htzamn3s3ovw7ujh@holly.lan \
    --to=daniel.thompson@linaro.org \
    --cc=hslester96@gmail.com \
    --cc=jason.wessel@windriver.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namit@vmware.com \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).