From: Mark Brown <broonie@kernel.org>
To: Gao Xiang <gaoxiang25@huawei.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-erofs@lists.ozlabs.org,
LKML <linux-kernel@vger.kernel.org>, Chao Yu <yuchao0@huawei.com>,
Miao Xie <miaoxie@huawei.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: erofs -next tree inclusion request
Date: Thu, 19 Sep 2019 13:17:39 +0100 [thread overview]
Message-ID: <20190919121739.GG3642@sirena.co.uk> (raw)
In-Reply-To: <20190919120110.GA48697@architecture4>
[-- Attachment #1: Type: text/plain, Size: 786 bytes --]
On Thu, Sep 19, 2019 at 08:01:10PM +0800, Gao Xiang wrote:
> Could you kindly help add the erofs -next tree to linux-next?
> git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git dev
> This can test all erofs patches with the latest linux-next tree
> and make erofs better...
That seems like a good idea however since we're in the merge window and
the only things that should be being added to -next right now are fixes
I'll hold off on doing this myself. Stephen will be back on the 30th
(just after merge window closes), I'm sure he'll be happy to add the
tree but in case this gets lost in all the mail from the time he's been
travelling you might want to remind him after that.
If you have a separate fixes branch I'd be happy to add that right now.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-09-19 12:17 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 [this message]
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
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=20190919121739.GG3642@sirena.co.uk \
--to=broonie@kernel.org \
--cc=gaoxiang25@huawei.com \
--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=yuchao0@huawei.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;
as well as URLs for NNTP newsgroup(s).