From: Jason Wessel <jason.wessel@windriver.com>
To: <torvalds@linux-foundation.org>
Cc: <linux-kernel@vger.kernel.org>, <kgdb-bugreport@lists.sourceforge.net>
Subject: [GIT PULL] KGDB/KDB fixes for 4.15-rc2
Date: Wed, 6 Dec 2017 16:33:43 -0600 [thread overview]
Message-ID: <1512599625-388-1-git-send-email-jason.wessel@windriver.com> (raw)
Linus,
Please pull the kgdb tree.
Summary of changes:
* Fix long standing problem with kdb kallsyms_symbol_next() return value
* Add new co-maintainer Daniel Thompson
git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/kgdb.git tags/for_linus-4.15-rc2
Thanks,
Jason.
The following changes since commit bebc6082da0a9f5d47a1ea2edc099bf671058bd4:
Linux 4.14 (2017-11-12 10:46:13 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/kgdb.git tags/for_linus-4.15-rc2
for you to fetch changes up to 4e23f78c74934e8ea624b59df58e646e0657608a:
kgdb/kdb/debug_core: Add co-maintainer Daniel Thompson (2017-12-06 16:12:43 -0600)
----------------------------------------------------------------
KGDB:
* Fix long standing problem with kdb kallsyms_symbol_next() return value
* Add new co-maintainer Daniel Thompson
----------------------------------------------------------------
Daniel Thompson (1):
kdb: Fix handling of kallsyms_symbol_next() return value
Jason Wessel (1):
kgdb/kdb/debug_core: Add co-maintainer Daniel Thompson
MAINTAINERS | 1 +
kernel/debug/kdb/kdb_io.c | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
next reply other threads:[~2017-12-06 22:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 22:33 Jason Wessel [this message]
2017-12-06 22:33 ` [PATCH 1/2] kdb: Fix handling of kallsyms_symbol_next() return value Jason Wessel
2017-12-06 22:33 ` [PATCH 2/2] kgdb/kdb/debug_core: Add co-maintainer Daniel Thompson Jason Wessel
2017-12-07 0:52 ` Randy Dunlap
2017-12-07 2:21 ` Jason Wessel
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=1512599625-388-1-git-send-email-jason.wessel@windriver.com \
--to=jason.wessel@windriver.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®