From: Sasha Levin <sashal@kernel.org>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Tomas Winkler <tomas.winkler@intel.com>,
Alexander Usyskin <alexander.usyskin@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org
Subject: Re: [char-misc for v4.5-rc2 2/2] mei: avoid FW version request on Ibex Peak and earlier
Date: Thu, 3 Oct 2019 07:31:22 -0400 [thread overview]
Message-ID: <20191003113122.GT17454@sasha-vm> (raw)
In-Reply-To: <73c1bac7-613e-6e89-646f-6e39ddfe58af@molgen.mpg.de>
On Thu, Oct 03, 2019 at 09:05:48AM +0200, Paul Menzel wrote:
>Dear Sasha,
>
>
>On 03.10.19 00:49, Sasha Levin wrote:
>
>>This commit has been processed because it contains a -stable tag.
>>The stable tag indicates that it's relevant for the following trees: 4.18+
>
>I’ll still need to test it.
>
>>The bot has tested the following trees: v5.3.1, v5.2.17, v4.19.75.
>>
>>v5.3.1: Build OK!
>>v5.2.17: Build OK!
>>v4.19.75: Failed to apply! Possible dependencies:
>> ce0925e8c2f8 ("mei: dma ring buffers allocation")
>>
>>
>>NOTE: The patch will not be queued to stable trees until it is upstream.
>>
>>How should we proceed with this patch?
>>
>>--
>>Thanks,
>>Sasha
>
>Could you please add a space after the two minuses: `-- `? That would
>make it a valid signature separator, and mail clients can strip it.
I thought there was a space there :( Now added... Thanks!
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-10-03 11:31 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 [this message]
2019-10-04 13:16 ` Greg Kroah-Hartman
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=20191003113122.GT17454@sasha-vm \
--to=sashal@kernel.org \
--cc=alexander.usyskin@intel.com \
--cc=gregkh@linuxfoundation.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 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.