Date:   Sat, 5 Feb 2022 10:47:47 +0100
From:   Greg KH <gregkh@linuxfoundation.org>
To:     Tabitha Sable <tabitha.c.sable@gmail.com>
Cc:     "Eric W. Biederman" <ebiederm@xmission.com>,
        Tejun Heo <tj@kernel.org>, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] cgroup-v1: Require capabilities to set
 release_agent" failed to apply to 4.9-stable tree
Message-ID: <Yf5Hw+ozu8p8uACd@kroah.com>
References: <164396325327225@kroah.com>
 <CAM62SmKNsDeCQuU7CPtu-rZw_58Sb1d917ibWKYAG2yakNU80g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAM62SmKNsDeCQuU7CPtu-rZw_58Sb1d917ibWKYAG2yakNU80g@mail.gmail.com>
Precedence: bulk

On Fri, Feb 04, 2022 at 11:28:19AM -0600, Tabitha Sable wrote:
> I'm happy to help with this, but I'm not familiar with the conventions for
> sending in backport diffs.
> 
> I've read through the docs on kernelnewbies and found them to be both
> overwhelmingly big and also not directly relevant to this particular
> situation. I think if I simply try to follow them I'll foul things up.

Yeah, it's not the same thing at all.

> Can I simply make the changes against the appropriate git branch, build and
> test, and then email in the diff to stable@vger.kernel.org copying most of
> what you've put in the original email, greg?

Yes, that's exactly what we need here.  Be sure to let me know what the
git id of the commit is in Linus's tree so we can properly track it (you
can put it in the changelog text somewhere.)

thanks,

greg k-h