public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: rostedt@goodmis.org, dzickus@redhat.com, mingo@kernel.org,
	tglx@linutronix.de, peterz@infradead.org
Subject: [PATCH 0/2] random debug patches
Date: Fri, 18 Mar 2016 16:28:02 +0100	[thread overview]
Message-ID: <20160318152802.407611377@infradead.org> (raw)

The only relation between these patches is that they are the result of me
trying to hunt down fail. Other than that they're unrelated and can be
independently applied.

             reply	other threads:[~2016-03-18 15:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-18 15:28 Peter Zijlstra [this message]
2016-03-18 15:28 ` [PATCH 1/2] watchdog: Fix output Peter Zijlstra
2016-03-18 16:37   ` Don Zickus
2016-03-18 16:44     ` Peter Zijlstra
2016-03-18 16:48       ` Peter Zijlstra
2016-03-18 17:42         ` Joe Perches
2016-03-18 18:12         ` Don Zickus
2016-03-18 17:49     ` Peter Zijlstra
2016-03-19  0:11       ` Jiri Kosina
2016-03-19  0:39         ` Jiri Kosina
2016-03-18 15:28 ` [PATCH 2/2] trace: Record and show NMI state Peter Zijlstra

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=20160318152802.407611377@infradead.org \
    --to=peterz@infradead.org \
    --cc=dzickus@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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