The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Dominique Martinet <asmadeus@codewreck.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	v9fs-developer@lists.sourceforge.net, linux-next@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [v9fs] Pull request for linux-next
Date: Thu, 19 Jul 2018 00:04:20 +1000	[thread overview]
Message-ID: <20180719000420.537d0290@canb.auug.org.au> (raw)
In-Reply-To: <20180718062920.GA7302@nautica>

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

Hi Dominique,

On Wed, 18 Jul 2018 08:29:20 +0200 Dominique Martinet <asmadeus@codewreck.org> wrote:
>
> I'd like to request that you add the following tree to linux-next:
> 
>   git://github.com/martinetd/linux 9p-next
> 
> 9p has seen some renewal of interest recently and I'd like to help take
> a bit of the burden off Andrew, who suggested getting this included in
> linux-next here[1].
> 
> This branch contains 9p filesystem & network patches that I have
> gathered recently after they have been reviewed, and will keep pushing
> patches there.
> 
> 
> I've tried to respect the rules I've found, but please tell me if I
> missed anything:
>  - all patches have the author's Signed-off-by tag,
>  - been posted to the v9fs and linux-kernel lists,
>  - have been reviewed,
>  - have been tested (*cough* a bit, I need to improve the process),
>  - and are destined to the 4.19 merge window
> 
> 
> [1] https://sourceforge.net/p/v9fs/mailman/message/36370423/

All looks good to me. Added from (later) today.

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

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

      reply	other threads:[~2018-07-18 14:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-18  6:29 [v9fs] Pull request for linux-next Dominique Martinet
2018-07-18 14:04 ` Stephen Rothwell [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=20180719000420.537d0290@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=akpm@linux-foundation.org \
    --cc=asmadeus@codewreck.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=v9fs-developer@lists.sourceforge.net \
    /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