From: Mimi Zohar <zohar@linux.ibm.com>
To: Tushar Sugandhi <tusharsu@linux.microsoft.com>,
Paul Moore <paul@paul-moore.com>
Cc: Stephen Smalley <stephen.smalley.work@gmail.com>,
SELinux <selinux@vger.kernel.org>,
Tyler Hicks <tyhicks@linux.microsoft.com>,
Lakshmi Ramasubramanian <nramas@linux.microsoft.com>,
linux-integrity@vger.kernel.org
Subject: Re: [RFC] Finding the right target branch for patches that span IMA and SeLinux
Date: Mon, 02 Nov 2020 11:35:57 -0500 [thread overview]
Message-ID: <66678394f824be5367cc0e1745f1bda98b436550.camel@linux.ibm.com> (raw)
In-Reply-To: <9195fd7a-a5c5-8588-d33c-772d2f530032@linux.microsoft.com>
On Sat, 2020-10-31 at 20:08 -0700, Tushar Sugandhi wrote:
> Hi Paul,
>
> On 2020-10-30 1:37 p.m., Paul Moore wrote:
> > On Fri, Oct 30, 2020 at 12:43 PM Tushar Sugandhi
> > <tusharsu@linux.microsoft.com> wrote:
> >>> Unless this patch set is specifically dependent on the two patches in
> >>> the SELinux tree beyond v5.10.0-rc1, please base it on v5.10.0-rc1.
> >>
> >> Thanks Mimi. We don't have dependencies on those two patches in SELinux
> >> tree.
> >>
> >> We'll base our changes on v5.10.0-rc1 in SELinux tree.
> >>
> >> Thanks for the quick response.
> >
> > I'm not as fast as Mimi, but I thought it might be worthwhile to
> > provide a bit more detail as to what I expect from SELinux kernel
> > submissions. I believe most other maintainers operate in a similar
> > manner, but I obviously can't speak for them.
> Thanks a lot for the detailed information Paul.
> Its very helpful, and we appreciate it.
> >
> > Unless there is an exception due to a previous discussion, I ask that
> > all SELinux kernel patches be based on either the selinux/next branch
> > or Linus' current tree. If your patch(set) applies cleanly to either
> > of those branches, and passes review, I'll merge it into the
> > selinux/next branch taking care of any merge conflicts that may arise.
> We will base on SeLinux -> next branch, as you/Mimi suggested.
Unless there was a compelling reason for basing it on the SELinux
branch, I asked that you base the changes on v5.10.0-rc1 (or later),
which has nothing to do with the SELinux branch. Once this patch set
is reviewed and ready to be upstreamed, a topic branch will be created
containing at least the IMA patches. The decision as to how the the
SELinux patch will be upstreamed will be made at that point. That
discussion will be between Paul and me.
thanks,
Mimi
next prev parent reply other threads:[~2020-11-02 16:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 23:33 [RFC] Finding the right target branch for patches that span IMA and SeLinux Tushar Sugandhi
2020-10-30 0:32 ` Mimi Zohar
2020-10-30 16:43 ` Tushar Sugandhi
2020-10-30 20:37 ` Paul Moore
2020-11-01 3:08 ` Tushar Sugandhi
2020-11-02 16:35 ` Mimi Zohar [this message]
2020-11-02 20:38 ` Tushar Sugandhi
2020-11-03 3:11 ` Paul Moore
2020-11-03 12:25 ` Mimi Zohar
2020-11-03 18:57 ` Lakshmi Ramasubramanian
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=66678394f824be5367cc0e1745f1bda98b436550.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=linux-integrity@vger.kernel.org \
--cc=nramas@linux.microsoft.com \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.org \
--cc=stephen.smalley.work@gmail.com \
--cc=tusharsu@linux.microsoft.com \
--cc=tyhicks@linux.microsoft.com \
/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