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
Date: Sat, 5 Feb 2022 10:47:47 +0100 [thread overview]
Message-ID: <Yf5Hw+ozu8p8uACd@kroah.com> (raw)
In-Reply-To: <CAM62SmKNsDeCQuU7CPtu-rZw_58Sb1d917ibWKYAG2yakNU80g@mail.gmail.com>
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
prev parent reply other threads:[~2022-02-05 9:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 8:27 FAILED: patch "[PATCH] cgroup-v1: Require capabilities to set release_agent" failed to apply to 4.9-stable tree gregkh
[not found] ` <CAM62SmKNsDeCQuU7CPtu-rZw_58Sb1d917ibWKYAG2yakNU80g@mail.gmail.com>
2022-02-05 9:47 ` Greg KH [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=Yf5Hw+ozu8p8uACd@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ebiederm@xmission.com \
--cc=stable@vger.kernel.org \
--cc=tabitha.c.sable@gmail.com \
--cc=tj@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.