All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhang Rui <rui.zhang@intel.com>
To: Brian Bian <brian.bian@linux.intel.com>,
	"edubezval@gmail.com" <edubezval@gmail.com>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: [PATCH] thermal: int3400_thermal: Ignore Unknown Notification Codes
Date: Wed, 27 Dec 2017 10:15:25 +0800	[thread overview]
Message-ID: <1514340925.2755.7.camel@intel.com> (raw)
In-Reply-To: <1510680996-25468-1-git-send-email-brian.bian@linux.intel.com>

On Tue, 2017-11-14 at 10:36 -0700, Brian Bian wrote:
> Some BIOS implementations route ACPI codes other than 0x83 to INT3400
> device. Ignore these ACPI notification codes because the INT3400
> driver
> does not handle them.
> 
> Signed-off-by: Brian Bian <brian.bian@linux.intel.com>

applied.

thanks,
rui
> ---
>  drivers/thermal/int340x_thermal/int3400_thermal.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/thermal/int340x_thermal/int3400_thermal.c
> b/drivers/thermal/int340x_thermal/int3400_thermal.c
> index 8ee38f5..c9db1c6 100644
> --- a/drivers/thermal/int340x_thermal/int3400_thermal.c
> +++ b/drivers/thermal/int340x_thermal/int3400_thermal.c
> @@ -211,7 +211,7 @@ static void int3400_notify(acpi_handle handle,
>  				thermal_prop);
>  		break;
>  	default:
> -		dev_err(&priv->adev->dev, "Unsupported event
> [0x%x]\n", event);
> +		/* Ignore unknown notification codes sent to INT3400
> device */
>  		break;
>  	}
>  }

      reply	other threads:[~2017-12-27  2:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-14 17:36 [PATCH] thermal: int3400_thermal: Ignore Unknown Notification Codes Brian Bian
2017-12-27  2:15 ` Zhang Rui [this message]

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=1514340925.2755.7.camel@intel.com \
    --to=rui.zhang@intel.com \
    --cc=brian.bian@linux.intel.com \
    --cc=edubezval@gmail.com \
    --cc=linux-pm@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.