From: Eric Biggers <ebiggers@google.com>
To: Sasha Levin <sashal@kernel.org>
Cc: stable-commits@vger.kernel.org, stable@vger.kernel.org
Subject: Re: Patch "ppp: mppe: Revert "ppp: mppe: Add softdep to arc4"" has been added to the 4.4-stable tree
Date: Sun, 24 May 2020 10:11:05 -0700 [thread overview]
Message-ID: <20200524171105.GA56504@google.com> (raw)
In-Reply-To: <20200524135255.8821820776@mail.kernel.org>
On Sun, May 24, 2020 at 09:52:54AM -0400, Sasha Levin wrote:
> This is a note to let you know that I've just added the patch titled
>
> ppp: mppe: Revert "ppp: mppe: Add softdep to arc4"
>
> to the 4.4-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:
> ppp-mppe-revert-ppp-mppe-add-softdep-to-arc4.patch
> and it can be found in the queue-4.4 subdirectory.
I already explained last time that this shouldn't be backported:
https://lore.kernel.org/stable/20190905161642.GA5659@google.com/
The commit message explains it too.
Is there something I could have done last time around to properly prevent this
from being backported, or do I have to continue to be ready to respond to these
emails which can come at arbitrary times forever?
>
> If you, or anyone else, feels it should not be added to the stable tree,
> please let <stable@vger.kernel.org> know about it.
Hard for "anyone else" to object to it when you didn't Cc any real mailing lists
(stable-commits doesn't count) and just sent this to me. Lucky I saw this.
- Eric
next parent reply other threads:[~2020-05-24 17:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200524135255.8821820776@mail.kernel.org>
2020-05-24 17:11 ` Eric Biggers [this message]
2020-05-25 2:43 ` Patch "ppp: mppe: Revert "ppp: mppe: Add softdep to arc4"" has been added to the 4.4-stable tree Sasha Levin
2020-05-26 19:09 ` Eric Biggers
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=20200524171105.GA56504@google.com \
--to=ebiggers@google.com \
--cc=sashal@kernel.org \
--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 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.