From: Gao Xiang <hsiangkao@aol.com>
To: Mark Brown <broonie@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-erofs@lists.ozlabs.org, Miao Xie <miaoxie@huawei.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-next@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: erofs -next tree inclusion request
Date: Thu, 19 Sep 2019 23:11:16 +0800 [thread overview]
Message-ID: <20190919150213.GA6138@hsiangkao-HP-ZHAN-66-Pro-G1> (raw)
In-Reply-To: <20190919145027.GN3642@sirena.co.uk>
On Thu, Sep 19, 2019 at 03:50:27PM +0100, Mark Brown wrote:
> On Thu, Sep 19, 2019 at 10:37:22PM +0800, Gao Xiang wrote:
>
> > The fixes only -fixes branch is
> > git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git fixes
>
> > Thanks for taking time on this stuff...
>
> OK, thanks - I've added that for tomorrow and I'll try to remember to
> add it onto the end of today's build too. Like I said before you might
> need to remind Stephen about the trees when he gets back on the 30th but
> hopefully he'll see these mails.
Thanks, I will keep eyes on -next branch and remind him when it's really
necessary.
>
> 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.
Yes, I understand these rules (by keeping up with several previous rounds)
and thanks for your reminder again.
>
> 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.
I will give a try after these commits are all solid and pull request with
my PGP key then... Thank you...
Thanks,
Gao Xiang
next prev parent reply other threads:[~2019-09-19 15:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 12:01 erofs -next tree inclusion request Gao Xiang
2019-09-19 12:17 ` Mark Brown
2019-09-19 12:23 ` Gao Xiang
2019-09-19 14:37 ` Gao Xiang
2019-09-19 14:50 ` Mark Brown
2019-09-19 15:11 ` Gao Xiang [this message]
2019-09-30 13:14 ` Stephen Rothwell
2019-09-30 13:32 ` Gao Xiang
2019-09-30 21:16 ` Stephen Rothwell
2019-09-30 21:18 ` Stephen Rothwell
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=20190919150213.GA6138@hsiangkao-HP-ZHAN-66-Pro-G1 \
--to=hsiangkao@aol.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=miaoxie@huawei.com \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).