public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Amir Goldstein <amir73il@gmail•com>
Cc: Christian Brauner <brauner@kernel•org>,
	Alessio Balsini <balsini@android•com>,
	Jens Axboe <axboe@kernel•dk>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>,
	Miklos Szeredi <miklos@szeredi•hu>
Subject: Re: linux-next: manual merge of the vfs-brauner tree with the overlayfs tree
Date: Tue, 26 Sep 2023 16:07:45 +1000	[thread overview]
Message-ID: <20230926160745.75df4606@canb.auug.org.au> (raw)
In-Reply-To: <CAOQ4uxgs7dCUQ50J6fwW5Dtgb-sBU4WyKogbU2PEG2uooWxSCw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]

Hi Amir,

On Tue, 26 Sep 2023 08:09:51 +0300 Amir Goldstein <amir73il@gmail•com> wrote:
>
> At this opportunity, I would like to ask you to add branch ovl-fixes
> from ssh://gitolite.kernel.org/pub/scm/linux/kernel/git/overlayfs/vfs.git
> to linux-next, because I will need to send some ovl fixes for 6.6 in
> the near future.

Added from tomorrow.

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. 

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 
     * 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.

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

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

next prev parent reply	other threads:[~2023-09-26  6:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-26  0:24 linux-next: manual merge of the vfs-brauner tree with the overlayfs tree Stephen Rothwell
2023-09-26  5:09 ` Amir Goldstein
2023-09-26  6:07   ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-09 23:50 Stephen Rothwell
2023-10-10  0:14 ` Stephen Rothwell
2023-10-10 11:28   ` Amir Goldstein

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=20230926160745.75df4606@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=amir73il@gmail$(echo .)com \
    --cc=axboe@kernel$(echo .)dk \
    --cc=balsini@android$(echo .)com \
    --cc=brauner@kernel$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=miklos@szeredi$(echo .)hu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox