From: Wim Van Sebroeck <wim@iguana.be>
To: Takahisa Tanaka <mc74hc00@gmail.com>
Cc: linux-watchdog@vger.kernel.org,
Paul Menzel <paulepanter@users.sourceforge.net>,
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>
Subject: Re: [PATCH 2/2] sp5100_tco: Write back the original value to reserved bits, instead of zero
Date: Wed, 30 Jan 2013 20:20:18 +0100 [thread overview]
Message-ID: <20130130192018.GB20100@spo001.leaseweb.com> (raw)
In-Reply-To: <1358128918-4415-2-git-send-email-mc74hc00@gmail.com>
Hi,
> In case of SP5100 or SB7x0 chipsets, the sp5100_tco module writes zero to
> reserved bits. The module, however, shouldn't depend on specific default
> value, and should perform a read-merge-write operation for the reserved
> bits.
>
> This patch makes the sp5100_tco module perform a read-merge-write operation
> on all the chipset (sp5100, sb7x0, sb8x0 or later).
>
> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=43176
> Signed-off-by: Takahisa Tanaka <mc74hc00@gmail.com>
Added to linux-watchdog-next.
Kind regards,
Wim.
next prev parent reply other threads:[~2013-01-30 19:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 2:01 [PATCH 1/2] sp5100_tco: Fix wrong indirect I/O access for getting value of reserved bits Takahisa Tanaka
2013-01-14 2:01 ` [PATCH 2/2] sp5100_tco: Write back the original value to reserved bits, instead of zero Takahisa Tanaka
2013-01-30 19:20 ` Wim Van Sebroeck [this message]
2013-01-31 13:43 ` t t
2013-01-30 19:19 ` [PATCH 1/2] sp5100_tco: Fix wrong indirect I/O access for getting value of reserved bits Wim Van Sebroeck
2013-02-06 8:46 ` Paul Menzel
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=20130130192018.GB20100@spo001.leaseweb.com \
--to=wim@iguana.be \
--cc=akpm@linux-foundation.org \
--cc=arekm@maven.pl \
--cc=bhelgaas@google.com \
--cc=florian@mickler.org \
--cc=jrnieder@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=mc74hc00@gmail.com \
--cc=paulepanter@users.sourceforge.net \
/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®