stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Tomas Winkler <tomas.winkler@intel.com>
Cc: Alexander Usyskin <alexander.usyskin@intel.com>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	Paul Menzel <pmenzel@molgen.mpg.de>
Subject: Re: [char-misc for v4.5-rc2 2/2] mei: avoid FW version request on Ibex Peak and earlier
Date: Fri, 4 Oct 2019 15:16:56 +0200	[thread overview]
Message-ID: <20191004131656.GA703365@kroah.com> (raw)
In-Reply-To: <20191001235958.19979-2-tomas.winkler@intel.com>

On Wed, Oct 02, 2019 at 02:59:58AM +0300, Tomas Winkler wrote:
> From: Alexander Usyskin <alexander.usyskin@intel.com>
> 
> The fixed MKHI client on PCH 6 gen platforms
> does not support fw version retrieval.
> The error is not fatal, but it fills up the kernel logs and
> slows down the driver start.
> This patch disables requesting FW version on GEN6 and earlier platforms.
> 
> Fixes warning:
> [   15.964298] mei mei::55213584-9a29-4916-badf-0fb7ed682aeb:01: Could not read FW version
> [   15.964301] mei mei::55213584-9a29-4916-badf-0fb7ed682aeb:01: version command failed -5
> 
> Cc: <stable@vger.kernel.org> +v4.18
> Cc: Paul Menzel <pmenzel@molgen.mpg.de>
> Signed-off-by: Alexander Usyskin <alexander.usyskin@intel.com>
> Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
> ---
>  drivers/misc/mei/bus-fixup.c | 16 +++++++++++++---
>  drivers/misc/mei/hw-me.c     | 21 ++++++++++++++++++---
>  drivers/misc/mei/hw-me.h     |  8 ++++++--
>  drivers/misc/mei/mei_dev.h   |  4 ++++
>  drivers/misc/mei/pci-me.c    | 10 +++++-----
>  5 files changed, 46 insertions(+), 13 deletions(-)
> 
> diff --git a/drivers/misc/mei/bus-fixup.c b/drivers/misc/mei/bus-fixup.c
> index 32e9b1aed2ca..5ac679ac9b19 100644
> --- a/drivers/misc/mei/bus-fixup.c
> +++ b/drivers/misc/mei/bus-fixup.c
> @@ -218,13 +218,23 @@ static void mei_mkhi_fix(struct mei_cl_device *cldev)
>  {
>  	int ret;
>  
> +	dev_dbg(&cldev->dev, "running hook %s\n", __func__);

That is what ftrace is for, don't sprinkle that all over the kernel for
no reason :(

thanks,

greg k-h

      parent reply	other threads:[~2019-10-04 13:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-01 23:59 [char-misc for 4.5-rc2 1/2] mei: me: add comet point (lake) LP device ids Tomas Winkler
2019-10-01 23:59 ` [char-misc for v4.5-rc2 2/2] mei: avoid FW version request on Ibex Peak and earlier Tomas Winkler
     [not found]   ` <20191002224947.A525221783@mail.kernel.org>
2019-10-03  7:05     ` Paul Menzel
2019-10-03 11:31       ` Sasha Levin
2019-10-04 13:16   ` Greg Kroah-Hartman [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=20191004131656.GA703365@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alexander.usyskin@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmenzel@molgen.mpg.de \
    --cc=stable@vger.kernel.org \
    --cc=tomas.winkler@intel.com \
    /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).