Linux-FSCrypt Archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Sasha Levin <sashal@kernel.org>,
	linux-fscrypt@vger.kernel.org, stable@vger.kernel.org
Subject: Re: Please don't backport "fscrypt: stop using keyrings subsystem for fscrypt_master_key" to stable until it's ready
Date: Tue, 18 Oct 2022 08:35:17 +0200	[thread overview]
Message-ID: <Y05JJZScBd5mZs6m@kroah.com> (raw)
In-Reply-To: <Y032gHb9LHSYtVBH@sol.localdomain>

On Mon, Oct 17, 2022 at 05:42:40PM -0700, Eric Biggers wrote:
> Hi Sasha,
> 
> Please stop backporting my commits to stable without asking, especially without
> Cc'ing to any mailing list that is archived on lore.kernel.org.
> 
> "fscrypt: stop using keyrings subsystem for fscrypt_master_key" is a big change,
> and there's already a fix for it pending
> (https://lore.kernel.org/r/20221011213838.209879-1-ebiggers@kernel.org).  I've
> been planning on doing the backports myself once the change has had a bit more
> time to soak, which is why I intentionally didn't add Cc stable.
> 
> It appears you also backported several other commits just to get it apply
> cleanly to 5.10, so please drop those too for now.

All now dropped from the queues, thanks.

greg k-h

      reply	other threads:[~2022-10-18  6:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18  0:42 Please don't backport "fscrypt: stop using keyrings subsystem for fscrypt_master_key" to stable until it's ready Eric Biggers
2022-10-18  6:35 ` 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=Y05JJZScBd5mZs6m@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=ebiggers@kernel.org \
    --cc=linux-fscrypt@vger.kernel.org \
    --cc=sashal@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).