From: Paul Menzel <paulepanter@users.sourceforge.net>
To: Takahisa Tanaka <mc74hc00@gmail.com>
Cc: linux-watchdog@vger.kernel.org, Wim Van Sebroeck <wim@iguana.be>,
Arkadiusz Miskiewicz <arekm@maven.pl>,
Bjorn Helgaas <bhelgaas@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jonathan Nieder <jrnieder@gmail.com>,
linux-kernel@vger.kernel.org,
Florian Mickler <florian@mickler.org>,
Joseph Salisbury <joseph.salisbury@canonical.com>,
Joseph Salisbury <josephtsalisbury@gmail.com>
Subject: Re: [PATCH v2] sp5100_tco: Remove code that may cause a boot failure
Date: Sun, 03 Mar 2013 10:40:21 +0100 [thread overview]
Message-ID: <1362303621.13011.14.camel@mattotaupa> (raw)
In-Reply-To: <1362289927-3635-1-git-send-email-mc74hc00@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1617 bytes --]
Dear Takahisa,
thank you for your patch.
Am Sonntag, den 03.03.2013, 14:52 +0900 schrieb Takahisa Tanaka:
> The critical problem which can't boot OS until the power is completely
> cut off found on PC with SB700 chipset.
As commented in my first reply – at least I think – please add the
mainboard model in here too.
Also add the commit (summary and hash) introducing this problem.
> This patch fix the problem, but,
• fix*es*
> this patch prevents the sp5100_tco driver from using watchdog timer
> function of chipset on PC with SP5100 or SB7x0 chipset.
I still do not understand it, as your patches were for SB8x0 support,
right?
> Re-programming the MMIO address registers for the watchdog timer must
> have generated the problem. However, I don't know root cause so far.
> So, I decided to remove the concerned codes.
>
> Note that this patch is dependent on the commit adbdcc03 and a6e26b13.
Please add the commit summaries, as a lot of people cannot memorize
commit hashes.
Is this patch exactly reverting these two patches?
> Link: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1116835
> Link: https://lkml.org/lkml/2013/2/14/271
>
> Signed-off-by: Takahisa Tanaka <mc74hc00@gmail.com>
As Linux 3.8 has been released, please add
CC: stable@vger.kernel.org
> ---
> v1 -> v2
> -The patch was split into the bug fix and the typo fix.
Thanks. Good idea.
> ---
> drivers/watchdog/sp5100_tco.c | 126 ++----------------------------------------
> 1 file changed, 6 insertions(+), 120 deletions(-)
[…]
Thanks,
Paul
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-03-03 9:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-03 5:52 Takahisa Tanaka
2013-03-03 9:40 ` Paul Menzel [this message]
2013-03-03 15:39 ` Tanaka Takahisa
2013-03-16 16:24 ` Tanaka Takahisa
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=1362303621.13011.14.camel@mattotaupa \
--to=paulepanter@users.sourceforge.net \
--cc=akpm@linux-foundation.org \
--cc=arekm@maven.pl \
--cc=bhelgaas@google.com \
--cc=florian@mickler.org \
--cc=joseph.salisbury@canonical.com \
--cc=josephtsalisbury@gmail.com \
--cc=jrnieder@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=mc74hc00@gmail.com \
--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
all inboxes | Powered by JetHome®