Hi Linux-next maintainers,
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...
Thank you very much,
Gao Xiang
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.
Hi Mark,
On Thu, Sep 19, 2019 at 01:17:39PM +0100, Mark Brown wrote:
> 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.
Thanks for the -fixes information and detailed reminder (I didn't notice
that, sorry...)
I will do a -fix only branch later for urgent and trivial fixes.
For -next, it's okay to wait for Stephen of course :) ...
Thanks,
Gao Xiang
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 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.
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
Hi Mark,
On Thu, Sep 19, 2019 at 08:23:28PM +0800, Gao Xiang wrote:
> Hi Mark,
>
> On Thu, Sep 19, 2019 at 01:17:39PM +0100, Mark Brown wrote:
> > 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.
>
> Thanks for the -fixes information and detailed reminder (I didn't notice
> that, sorry...)
>
> I will do a -fix only branch later for urgent and trivial fixes.
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...
Thanks,
Gao Xiang
>
> For -next, it's okay to wait for Stephen of course :) ...
>
> Thanks,
> Gao Xiang
>
Hi Gao,
On Thu, 19 Sep 2019 22:37:22 +0800 Gao Xiang <[email protected]> wrote:
>
> The fixes only -fixes branch is
> git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git fixes
I have added this from tomorrow (sorry for the drop out today).
Which address(es) should I use as your contact address(es)?
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
[email protected]
Hi Stephen,
On Mon, Sep 30, 2019 at 11:14:39PM +1000, Stephen Rothwell wrote:
> Hi Gao,
>
> On Thu, 19 Sep 2019 22:37:22 +0800 Gao Xiang <[email protected]> wrote:
> >
> > The fixes only -fixes branch is
> > git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git fixes
>
> I have added this from tomorrow (sorry for the drop out today).
That is ok, and thanks for your great work.
>
> Which address(es) should I use as your contact address(es)?
I think [email protected] is preferred since it can always redirect
to my workable email address.
>
> 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.
Thanks for the kind reminder :)
Thanks,
Gao Xiang
Hi Gao,
On Mon, 30 Sep 2019 21:32:22 +0800 Gao Xiang <[email protected]> wrote:
>
> I think [email protected] is preferred since it can always redirect
> to my workable email address.
OK, done.
--
Cheers,
Stephen Rothwell
Hi Gao,
On Thu, 19 Sep 2019 20:01:10 +0800 Gao Xiang <[email protected]> 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...
Added from 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
[email protected]