From: Alexander Holler <holler@ahsoftware.de>
To: Bryan Wu <bryan.wu@canonical.com>
Cc: linux-kernel@vger.kernel.org, Shuah Khan <shuahkhan@gmail.com>,
Richard Purdie <rpurdie@rpsys.net>,
Feng Tang <feng.tang@intel.com>
Subject: Re: [PATCH] leds: heartbeat: fix bug on panic
Date: Wed, 04 Jul 2012 09:51:31 +0200 [thread overview]
Message-ID: <4FF3F603.6080401@ahsoftware.de> (raw)
In-Reply-To: <CAK5ve-LZdCtUC3inX9S-UGwHBLxS-hqLmmUBOkTBn-9Z--7oPw@mail.gmail.com>
Am 04.07.2012 09:29, schrieb Bryan Wu:
> Anyway, I will apply this patch to my for-next branch.
Is it already too late for 3.5 (where I introduced the bug)? I know I
should have reacted faster, but I the bug report got down under a ton of
other mails. ;)
Regards,
Alexander
next prev parent reply other threads:[~2012-07-04 7:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 8:26 [BUG]INFO: suspicious RCU usage for 3.5-rc1+ Feng Tang
2012-07-02 21:41 ` Alexander Holler
2012-07-03 6:35 ` [PATCH] leds: heartbeat: fix bug on panic Alexander Holler
2012-07-04 7:05 ` Bryan Wu
2012-07-04 7:11 ` Alexander Holler
2012-07-04 7:29 ` Bryan Wu
2012-07-04 7:51 ` Alexander Holler [this message]
2012-07-04 7:54 ` Bryan Wu
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=4FF3F603.6080401@ahsoftware.de \
--to=holler@ahsoftware.de \
--cc=bryan.wu@canonical.com \
--cc=feng.tang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpurdie@rpsys.net \
--cc=shuahkhan@gmail.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