From: Jason Wessel <jason.wessel@windriver.com>
To: mingo@elte.hu, peterz@infradead.org
Cc: kgdb-bugreport@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: [GIT PULL] softlockup kgdb fix for tip for 2.6.34
Date: Thu, 21 Jan 2010 11:26:30 -0600 [thread overview]
Message-ID: <1264094791-8883-1-git-send-email-jason.wessel@windriver.com> (raw)
Ingo, would it be possible to pull in this change or recommend what
needs to be done to reach closure on this long standing problem.
git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/linux-2.6-kgdb.git for_igno
This particular fix for kgdb to allows it to work correctly with the
softlockup code. It has been around since September 2009 and in
linux-next since the creation of the patch. I never issued a pull to
the Linus tree because I did not get an ack from either yourself or
Peter.
Thanks,
Jason.
---
short log follows:
The following changes since commit 24bc7347da73a9ed3383056c3d0f28c0e361621e:
Linus Torvalds (1):
Merge git://git.kernel.org/.../wim/linux-2.6-watchdog
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/linux-2.6-kgdb.git for_ingo
Jason Wessel (1):
softlockup: add sched_clock_tick() to avoid kernel warning on kgdb resume
include/linux/sched.h | 4 ++++
kernel/kgdb.c | 6 +++---
kernel/softlockup.c | 15 +++++++++++++++
3 files changed, 22 insertions(+), 3 deletions(-)
next reply other threads:[~2010-01-21 17:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 17:26 Jason Wessel [this message]
2010-01-21 17:26 ` [PATCH 1/1] softlockup: add sched_clock_tick() to avoid kernel warning on kgdb resume 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=1264094791-8883-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=mingo@elte.hu \
--cc=peterz@infradead.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®