Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Sat, 9 May 2020 10:00:21 +1000
From:   Stephen Rothwell <sfr@canb.auug.org.au>
To:     Mimi Zohar <zohar@linux.ibm.com>
Cc:     Linux Next Mailing List <linux-next@vger.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Adding a linux-integrity "fixes" branch
Message-ID: <20200509100021.4d79b426@canb.auug.org.au>
In-Reply-To: <1588906186.6053.10.camel@linux.ibm.com>
References: <1588906186.6053.10.camel@linux.ibm.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="Sig_/a5DsUSi7kTNw1wVepPEAkMX";
 protocol="application/pgp-signature"; micalg=pgp-sha256
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

--Sig_/a5DsUSi7kTNw1wVepPEAkMX
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hi Mimi,

On Thu, 07 May 2020 22:49:46 -0400 Mimi Zohar <zohar@linux.ibm.com> wrote:
>
> In addition to the existing "next-integrity" branch, could you add the
> "fixes" branch?

Added from Monday.

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgement of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window.=20

You will need to ensure that the patches/commits in your tree/series have
been:
     * submitted under GPL v2 (or later) and include the Contributor's
        Signed-off-by,
     * posted to the relevant mailing list,
     * reviewed by you (or another maintainer of your subsystem tree),
     * successfully unit tested, and=20
     * destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

--=20
Cheers,
Stephen Rothwell=20
sfr@canb.auug.org.au

--Sig_/a5DsUSi7kTNw1wVepPEAkMX
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAl618pUACgkQAVBC80lX
0GwezAf+OqtayFjhJC8oP+xXOxPLRZVj8PTwUs5H+rWKtDcWrAVietalzziFUqfU
5t1+lnb1QYbvph49OwV0uBDGkXYtw+ulSD3l13WhLcHt9eQ3EUMot92wcMXbh8vE
CsCiiEeL8fucFZ79wQiEQ6Ie2VzepRKX0qFHGZFok9QWFPuTAgRHcHvaNVcSam+b
lXf7FqXz7D8OwiBkeV+U1er5v6ZA57W9OdsIh4yrsvuruVDLHSuVqJEM59rsTmK9
xFFR7ak1Ozqf4f+TafxbT86iRbZLVrxIMOKh5JQaTC8DdzkDz0XqDf4CNJtG4G8s
hU6UrpAeoaq51DTdFcZJlMj7vm+D5A==
=eYfc
-----END PGP SIGNATURE-----

--Sig_/a5DsUSi7kTNw1wVepPEAkMX--