Re: [PATCH] thermal: fix build error at thermal_sys.c

From: Zhang Rui
Date: Mon Jul 23 2012 - 03:26:42 EST

On ä, 2012-07-23 at 08:54 +0200, Jean Delvare wrote:
> Hi Rui,
> On Mon, 23 Jul 2012 10:02:16 +0800, Zhang Rui wrote:
> > BTW: what is the rule for linux-next?
> > I refreshed the patches, did some test, and sent to mailing list
> > saying that I want to push them to linux-next, please review.
> > And then I got bug report from linux-next...
> > shouldn't them be merged after I sending git pull request?
> Your tree is set for linux-next inclusion.
> This means that, every day,
> the current state of (one branch of) your tree makes it into that day's
> linux-next. linux-next receives some testing so you may receive bug
> reports that way (most frequently merge and build issues.)
> But patches don't go from linux-next to Linus's upstream tree
> automatically. Whenever you want your patches to actually go to Linus,
> you must ask Linus explicitly to pull them.
> So, when a build issue is found in linux-next, the right thing to do is
> to blast the faulty branch and recreate it without the build breakage,
> then have it go in at least one linux-next iterations to make sure you
> did get things right this time, and only then ask Linus to pull from
> your branch.
I know they should stay in linux-next for a while before asking Linus to
pull them, but I did not expect them to go into linux-next immediately
when I submitted all the patches into my next branch and sent out for

so "my tree is set for linux-next inclusion" means that, all the stuff
will be merged in linux-next automatically, even if I have not asked
linux-next to pull my changes, right?

sorry for the mistake again.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at