We are considering freezing the 11.11 kernel this next Monday (Nov 14) in order to release it on Wednesday (Nov 16), so it is out there before the US Thanksgiving holiday.
If anyone would like to see their patches included in the Linaro kernel for this month, please consider submitting them ASAP.
As discussed in Orlando, we are also considering a shift towards using the latest tagged release from Torvalds' mainline tree. This process is not fully in place yet, so the regular Linaro release based on the latest stable upstream release will still occur for this month.
Nicolas
On Wed, Nov 9, 2011 at 12:59 AM, Nicolas Pitre nicolas.pitre@linaro.org wrote:
We are considering freezing the 11.11 kernel this next Monday (Nov 14) in order to release it on Wednesday (Nov 16), so it is out there before the US Thanksgiving holiday.
If anyone would like to see their patches included in the Linaro kernel for this month, please consider submitting them ASAP.
As discussed in Orlando, we are also considering a shift towards using the latest tagged release from Torvalds' mainline tree. This process is not fully in place yet, so the regular Linaro release based on the latest stable upstream release will still occur for this month.
Vincent, Amit:
Could you please ensure that sched_mc optimisation and samsung cpuidle patches are integrated and enabled into Nico's tree?
Mike:
Any chance of getting a preview of common clk on a separate branch and asking the platform team to create a build for it?
Rob, Daniel: Same thing for cpuidle core + imx changes as Mike.
On Tue, Nov 8, 2011 at 11:25 PM, Amit Kucheria amit.kucheria@linaro.org wrote:
On Wed, Nov 9, 2011 at 12:59 AM, Nicolas Pitre nicolas.pitre@linaro.org wrote:
We are considering freezing the 11.11 kernel this next Monday (Nov 14) in order to release it on Wednesday (Nov 16), so it is out there before the US Thanksgiving holiday.
If anyone would like to see their patches included in the Linaro kernel for this month, please consider submitting them ASAP.
As discussed in Orlando, we are also considering a shift towards using the latest tagged release from Torvalds' mainline tree. This process is not fully in place yet, so the regular Linaro release based on the latest stable upstream release will still occur for this month.
Vincent, Amit:
Could you please ensure that sched_mc optimisation and samsung cpuidle patches are integrated and enabled into Nico's tree?
Mike:
Any chance of getting a preview of common clk on a separate branch and asking the platform team to create a build for it?
My common clk code is rebased onto Linus' v3.2-rc1 tag. I think it's best for me to skip this Linaro tree "merge window" and focus on upstreaming them. Once the Linaro kernel catches up to ToT then porting them over should be trivial.
Regards, Mike
Rob, Daniel: Same thing for cpuidle core + imx changes as Mike.
Hi Nicolas,
Please pull the samsung cpuidle code from,
(git://git.linaro.org/people/amitdanielk/linux.git branch: samsung_cpuidle_l2_retention).
The above branch is rebased on top of your tree and contains some necessary patches already in mainline.
All these patches are submitted and under review(http://www.spinics.net/lists/arm-kernel/msg146579.html).
Thanks, Amit Daniel
On 9 November 2011 12:55, Amit Kucheria amit.kucheria@linaro.org wrote:
On Wed, Nov 9, 2011 at 12:59 AM, Nicolas Pitre nicolas.pitre@linaro.org wrote:
We are considering freezing the 11.11 kernel this next Monday (Nov 14) in order to release it on Wednesday (Nov 16), so it is out there before the US Thanksgiving holiday.
If anyone would like to see their patches included in the Linaro kernel for this month, please consider submitting them ASAP.
As discussed in Orlando, we are also considering a shift towards using the latest tagged release from Torvalds' mainline tree. This process is not fully in place yet, so the regular Linaro release based on the latest stable upstream release will still occur for this month.
Vincent, Amit:
Could you please ensure that sched_mc optimisation and samsung cpuidle patches are integrated and enabled into Nico's tree?
Mike:
Any chance of getting a preview of common clk on a separate branch and asking the platform team to create a build for it?
Rob, Daniel: Same thing for cpuidle core + imx changes as Mike.
Hi Nicolas,
Could you pull the sched_mc code from
git://git.linaro.org/people/vingu/kernel.git on the branch sched_mc_for_11.11
This branch is rebased on your tree and contains sched_mc optimization code as well as some patches, which are in mainline. These additional patches solve various issues on features that are used by sched_mc optimization.
Regards, Vincent
On 9 November 2011 08:25, Amit Kucheria amit.kucheria@linaro.org wrote:
On Wed, Nov 9, 2011 at 12:59 AM, Nicolas Pitre nicolas.pitre@linaro.org wrote:
We are considering freezing the 11.11 kernel this next Monday (Nov 14) in order to release it on Wednesday (Nov 16), so it is out there before the US Thanksgiving holiday.
If anyone would like to see their patches included in the Linaro kernel for this month, please consider submitting them ASAP.
As discussed in Orlando, we are also considering a shift towards using the latest tagged release from Torvalds' mainline tree. This process is not fully in place yet, so the regular Linaro release based on the latest stable upstream release will still occur for this month.
Vincent, Amit:
Could you please ensure that sched_mc optimisation and samsung cpuidle patches are integrated and enabled into Nico's tree?
Mike:
Any chance of getting a preview of common clk on a separate branch and asking the platform team to create a build for it?
Rob, Daniel: Same thing for cpuidle core + imx changes as Mike.
On Mon, 14 Nov 2011, Vincent Guittot wrote:
Hi Nicolas,
Could you pull the sched_mc code from
git://git.linaro.org/people/vingu/kernel.git on the branch sched_mc_for_11.11
This branch is rebased on your tree and contains sched_mc optimization code as well as some patches, which are in mainline. These additional patches solve various issues on features that are used by sched_mc optimization.
OK, merged and pushed out.
I however have some suggestions for next time:
1. When including mainline patches, please include a reference to the original commit ID in the commit message of the included patch.
2. Please try to be more explicit about the reasons for your commits, especially those which are not immediately obvious. Stating _what_ you are doing is good, but elaborating a bit more on _why_ is even more important for reviewers.
3. Try to gather some acked-by/reviewed-by tags so at least someone else more familiar with the issues at hand is confirming the goodness of your patch. I'm not able to make that judgement call alone for everything.
Thanks
Nicolas
On 14 November 2011 16:37, Nicolas Pitre nicolas.pitre@linaro.org wrote:
On Mon, 14 Nov 2011, Vincent Guittot wrote:
Hi Nicolas,
Could you pull the sched_mc code from
git://git.linaro.org/people/vingu/kernel.git on the branch sched_mc_for_11.11
This branch is rebased on your tree and contains sched_mc optimization code as well as some patches, which are in mainline. These additional patches solve various issues on features that are used by sched_mc optimization.
OK, merged and pushed out.
I however have some suggestions for next time:
- When including mainline patches, please include a reference to the
original commit ID in the commit message of the included patch.
- Please try to be more explicit about the reasons for your commits,
especially those which are not immediately obvious. Stating _what_ you are doing is good, but elaborating a bit more on _why_ is even more important for reviewers.
- Try to gather some acked-by/reviewed-by tags so at least someone else
more familiar with the issues at hand is confirming the goodness of your patch. I'm not able to make that judgement call alone for everything.
ok, I will take your suggestion into account for the next time
Thanks,
-
Amit Kachhap -
Amit Kucheria -
Mike Turquette -
Nicolas Pitre -
Vincent Guittot