From: Sasha Levin <sashal@kernel.org>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: stable-commits@vger.kernel.org,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: Patch "soc: fsl: qe: change return type of cpm_muram_alloc() to s32" has been added to the 5.5-stable tree
Date: Fri, 21 Feb 2020 08:46:04 -0500 [thread overview]
Message-ID: <20200221134604.GL1734@sasha-vm> (raw)
In-Reply-To: <89ccc850-54af-aaec-4a9e-330dcb814ca7@rasmusvillemoes.dk>
On Fri, Feb 21, 2020 at 09:53:04AM +0100, Rasmus Villemoes wrote:
>On 21/02/2020 02.27, Sasha Levin wrote:
>> This is a note to let you know that I've just added the patch titled
>>
>> soc: fsl: qe: change return type of cpm_muram_alloc() to s32
>>
>> to the 5.5-stable tree which can be found at:
>> http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>>
>> The filename of the patch is:
>> soc-fsl-qe-change-return-type-of-cpm_muram_alloc-to-.patch
>> and it can be found in the queue-5.5 subdirectory.
>>
>> If you, or anyone else, feels it should not be added to the stable tree,
>> please let <stable@vger.kernel.org> know about it.
>
>Isn't that what I did when I replied to the AUTOSEL mail a week ago?
>
>https://lore.kernel.org/stable/a920b57f-ad9e-5c25-3981-0462febd952a@rasmusvillemoes.dk/
>
>The TL;DR is the last part of the middle paragraph "... I think they
>should not be added to any -stable kernel."
You did and I've missed your mail, sorry. I'll drop it now.
--
Thanks,
Sasha
next prev parent reply other threads:[~2020-02-21 13:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200221012743.D5A0E208E4@mail.kernel.org>
2020-02-21 8:53 ` Patch "soc: fsl: qe: change return type of cpm_muram_alloc() to s32" has been added to the 5.5-stable tree Rasmus Villemoes
2020-02-21 13:46 ` Sasha Levin [this message]
2020-02-24 8:23 ` Rasmus Villemoes
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=20200221134604.GL1734@sasha-vm \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux@rasmusvillemoes.dk \
--cc=stable-commits@vger.kernel.org \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox