From: CAI Qian <caiqian@redhat.com>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: Rob Herring <robh@kernel.org>,
Alessandro Zummo <a.zummo@towertech.it>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
rtc-linux@googlegroups.com,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [4.9-rc1] kernel panic from `cat /proc/driver/rtc`
Date: Tue, 18 Oct 2016 15:58:41 -0400 (EDT) [thread overview]
Message-ID: <1380748808.370638.1476820721453.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20161018192014.sqekbhk66b5ne7jy@piout.net>
> Is that fixed by http://patchwork.ozlabs.org/patch/683728/ ?
Yup.
prev parent reply other threads:[~2016-10-18 19:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <406701477.279464.1476797119876.JavaMail.zimbra@redhat.com>
2016-10-18 13:28 ` [4.9-rc1] kernel panic from `cat /proc/driver/rtc` CAI Qian
2016-10-18 18:47 ` CAI Qian
2016-10-18 19:20 ` Alexandre Belloni
2016-10-18 19:58 ` CAI Qian [this message]
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=1380748808.370638.1476820721453.JavaMail.zimbra@redhat.com \
--to=caiqian@redhat.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=rtc-linux@googlegroups.com \
/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