From: Peter Zijlstra <peterz@infradead.org>
To: Matteo Croce <mcroce@redhat.com>
Cc: x86@kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-sound@vger.kernel.org, platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH 0/4] Introduce the aural error reporting framework
Date: Mon, 1 Apr 2019 13:03:29 +0200 [thread overview]
Message-ID: <20190401110329.GA12232@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20190401102456.11162-1-mcroce@redhat.com>
On Mon, Apr 01, 2019 at 12:24:51PM +0200, Matteo Croce wrote:
> The buzzer driver is simple, requires just a few register writes to work,
> the hardware is extremely cheap and is already present on most machines.
What, no morse-code register dumps?
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: Matteo Croce <mcroce@redhat.com>
Cc: x86@kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-sound@vger.kernel.org, platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH 0/4] Introduce the aural error reporting framework
Date: Mon, 01 Apr 2019 11:03:29 +0000 [thread overview]
Message-ID: <20190401110329.GA12232@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20190401102456.11162-1-mcroce@redhat.com>
On Mon, Apr 01, 2019 at 12:24:51PM +0200, Matteo Croce wrote:
> The buzzer driver is simple, requires just a few register writes to work,
> the hardware is extremely cheap and is already present on most machines.
What, no morse-code register dumps?
next prev parent reply other threads:[~2019-04-01 11:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 10:24 [PATCH 0/4] Introduce the aural error reporting framework Matteo Croce
2019-04-01 10:24 ` Matteo Croce
2019-04-01 10:24 ` [PATCH 1/4] " Matteo Croce
2019-04-01 10:24 ` Matteo Croce
2019-04-01 10:24 ` [PATCH 2/4] panic: use the aural error reporting framework to report panics Matteo Croce
2019-04-01 10:24 ` Matteo Croce
2019-04-01 10:24 ` [PATCH 3/4] bug: use the aural error reporting framework to report warnings Matteo Croce
2019-04-01 10:24 ` Matteo Croce
2019-04-01 10:24 ` [PATCH 4/4] oops: use the aural error reporting framework to report oopses Matteo Croce
2019-04-01 10:24 ` Matteo Croce
2019-04-01 10:24 ` [PATCH 5/4] procfs: utility handler to trigger different errors Matteo Croce
2019-04-01 10:24 ` Matteo Croce
2019-04-01 11:03 ` Peter Zijlstra [this message]
2019-04-01 11:03 ` [PATCH 0/4] Introduce the aural error reporting framework Peter Zijlstra
2019-04-02 8:49 ` Thomas Gleixner
2019-04-02 8:49 ` Thomas Gleixner
2019-04-02 11:50 ` Matteo Croce
2019-04-02 11:50 ` Matteo Croce
2019-04-02 13:21 ` Thomas Gleixner
2019-04-02 13:21 ` Thomas Gleixner
2019-04-01 13:45 ` Emiliano Russo
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=20190401110329.GA12232@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=mcroce@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.