linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Thomas Bächler" <thomas@archlinux.org>
To: Feng Tang <feng.79.tang@gmail.com>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
	Peter Tyser <ptyser@xes-inc.com>,
	Wim Van Sebroeck <wim@iguana.be>,
	Aaron Sierra <asierra@xes-inc.com>,
	Guenter Roeck <linux@roeck-us.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-watchdog@vger.kernel.org,
	Tobias Powalowski <tpowa@archlinux.org>
Subject: Re: Serious regression in 3.5's iTCO_wdt, does anyone care?
Date: Thu, 23 Aug 2012 16:46:08 +0200	[thread overview]
Message-ID: <50364230.2070606@archlinux.org> (raw)
In-Reply-To: <CA++bM2tMVLQLn2=_MwhEp79xJpj6fjz+Smd5ZpE5dLKObe+hCw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1381 bytes --]

Am 23.08.2012 16:35, schrieb Feng Tang:
> 2012/8/23 Thomas Bächler <thomas@archlinux.org>:
>> This regards the following commit in the Linus tree:
>>
>> commit 887c8ec7219fc8eba78bb8f44a74c660934e9b98
>> Author: Aaron Sierra <asierra@xes-inc.com>
>> Date:   Fri Apr 20 14:14:11 2012 -0500
>>
>>     watchdog: Convert iTCO_wdt driver to mfd model
>>
>> Ever since the Linux 3.5 update, the iTCO_wdt driver has been completely
>> non-functional on every machine I encountered due to the above
>> conversion. A bug report for this problem has been open at
>> https://bugzilla.kernel.org/show_bug.cgi?id=44991 for over a month.
>>
>> Yet, neither the author of the commit, nor the people who signed off on
>> it have reacted to the bug report.
>>
>> At this point, I believe that none of you are actually aware of the
>> problem and I write you to change that unfortunate situation.
> 
> There is already a patch posted for this bug, pls check
> https://lkml.org/lkml/2012/8/14/309
> and the discussion

And there I thought I had searched the LKML for lpc_ich and iTCO_wdt.
Apparently my last search was more than a week ago.

Would have been nice if you posted the link to the discussion into the
bug report, this would have saved me (and others) some trouble.

Thanks anyway, the discussion has all the information I needed. Sorry
for the noise.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]

  reply	other threads:[~2012-08-23 14:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-23 14:15 Serious regression in 3.5's iTCO_wdt, does anyone care? Thomas Bächler
2012-08-23 14:35 ` Feng Tang
2012-08-23 14:46   ` Thomas Bächler [this message]
2012-08-23 17:18 ` Samuel Ortiz

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=50364230.2070606@archlinux.org \
    --to=thomas@archlinux.org \
    --cc=asierra@xes-inc.com \
    --cc=feng.79.tang@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=ptyser@xes-inc.com \
    --cc=sameo@linux.intel.com \
    --cc=tpowa@archlinux.org \
    --cc=wim@iguana.be \
    /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;
as well as URLs for NNTP newsgroup(s).