From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Tomas Winkler <tomas.winkler@intel.com>
Cc: Alexander Usyskin <alexander.usyskin@intel.com>,
Vitaly Lubart <vitaly.lubart@intel.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [char-misc 1/4] mei: me: disable driver on the ign firmware
Date: Tue, 15 Feb 2022 11:24:14 +0100 [thread overview]
Message-ID: <Ygt/Th1UeOkWpwlD@kroah.com> (raw)
In-Reply-To: <20220215080438.264876-1-tomas.winkler@intel.com>
On Tue, Feb 15, 2022 at 10:04:35AM +0200, Tomas Winkler wrote:
> From: Alexander Usyskin <alexander.usyskin@intel.com>
>
> Add a quirk to disable MEI interface on Intel PCH Ignition (IGN)
> as the IGN firmware doesn't support the protocol.
>
> Cc: <stable@vger.kernel.org>
> Signed-off-by: Alexander Usyskin <alexander.usyskin@intel.com>
> Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
> ---
> drivers/misc/mei/hw-me-regs.h | 1 +
> drivers/misc/mei/hw-me.c | 23 ++++++++++++-----------
> 2 files changed, 13 insertions(+), 11 deletions(-)
I see 2 different copies of this patch/email:
https://lore.kernel.org/all/20220215075748.264195-1-tomas.winkler@intel.com/
https://lore.kernel.org/all/20220215080438.264876-1-tomas.winkler@intel.com/
which one is right?
confused,
greg k-h
next prev parent reply other threads:[~2022-02-15 10:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 8:04 [char-misc 1/4] mei: me: disable driver on the ign firmware Tomas Winkler
2022-02-15 8:04 ` [char-misc-next 2/4] mei: me: avoid link reset on shutdown Tomas Winkler
2022-02-15 8:04 ` [char-misc-next 3/4] mei: me: fix reset policy on read error in interrupt Tomas Winkler
2022-02-15 8:04 ` [char-misc-next 4/4] mei: do not overwrite state on hw start Tomas Winkler
2022-02-15 10:24 ` Greg Kroah-Hartman [this message]
2022-02-15 13:56 ` [char-misc 1/4] mei: me: disable driver on the ign firmware Winkler, Tomas
-- strict thread matches above, loose matches on Subject: below --
2022-02-15 7:57 Tomas Winkler
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=Ygt/Th1UeOkWpwlD@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexander.usyskin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tomas.winkler@intel.com \
--cc=vitaly.lubart@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 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.