linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Lucas Stach <dev@lynxeye.de>, Wim Van Sebroeck <wim@iguana.be>,
	linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sp5100_tco: properly check for new register layouts
Date: Fri, 13 May 2016 16:27:09 +0200	[thread overview]
Message-ID: <s5h8tze9goy.wl-tiwai@suse.de> (raw)
In-Reply-To: <572961D5.6060507@roeck-us.net>

On Wed, 04 May 2016 04:43:33 +0200,
Guenter Roeck wrote:
> 
> On 05/03/2016 10:15 AM, Lucas Stach wrote:
> > Commits 190aa4304de6 (Add AMD Mullins platform support) and
> > cca118fa2a0a94 (Add AMD Carrizo platform support) enabled the
> > driver on a lot more devices, but the following commit missed
> > a single location in the code when checking if the SB800 register
> > offsets should be used. This leads to the wrong register being
> > written which in turn causes ACPI to go haywire.
> >
> > Fix this by introducing a helper function to check for the new
> > register layout and use this consistently.
> >
> > https://bugzilla.kernel.org/show_bug.cgi?id=114201
> > https://bugzilla.redhat.com/show_bug.cgi?id=1329910
> > Fixes: bdecfcdb5461 (sp5100_tco: fix the device check for SB800
> > and later chipsets)
> > Cc: stable@vger.kernel.org (4.5+)
> > Signed-off-by: Lucas Stach <dev@lynxeye.de>
> 
> Reviewed-by: Guenter Roeck <linux@roeck-us.net>

What is the status of this patch?  I still can't find it in
linux-next.

We've got more and more bug reports about this, so would love to get
this resolved soonish.


thanks,

Takashi

  reply	other threads:[~2016-05-13 14:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-03 17:15 [PATCH] sp5100_tco: properly check for new register layouts Lucas Stach
2016-05-04  2:43 ` Guenter Roeck
2016-05-13 14:27   ` Takashi Iwai [this message]
2016-05-14 16:44 ` Wim Van Sebroeck

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=s5h8tze9goy.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=dev@lynxeye.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --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).