On 5 August 2013 10:45, Andy Green andy.gr...@linaro.org wrote:
Hi Mark -
I have some small practical questions about LSK. I was able to make a
tree with our linux-linaro-core-tracking@v3.10 LT patches on LSK basis
work well (so far).
I found this repo (it needs its ./description updating)
On Mon, 2013-08-05 at 10:45 +0800, Andy Green wrote:
2) I saw the vexpress integration stuff from ARM LT was included
already which is good, is there a wiki page (or README.html or the
gitweb is also good) explaining the composition?
The vexpress branch is basicall the same as what is in
On Mon, 2013-08-05 at 16:43 +0800, Andy Green wrote:
On 5 August 2013 10:45, Andy Green andy.gr...@linaro.org wrote:
Hi Mark -
I have some small practical questions about LSK. I was able to make a
tree with our linux-linaro-core-tracking@v3.10 LT patches on LSK basis
work well (so
On 5 August 2013 16:58, Jon Medhurst (Tixy) t...@linaro.org wrote:
On Mon, 2013-08-05 at 10:45 +0800, Andy Green wrote:
2) I saw the vexpress integration stuff from ARM LT was included
already which is good, is there a wiki page (or README.html or the
gitweb is also good) explaining the
On Mon, 2013-08-05 at 17:13 +0800, Andy Green wrote:
On 5 August 2013 16:58, Jon Medhurst (Tixy) t...@linaro.org wrote:
tracking-armlt-cci
CCI driver and CCI PMU patches.
We started using that the other day trying to track down a nasty bug,
I didn't even know we got it from
On 5 August 2013 10:11, Jon Medhurst (Tixy) t...@linaro.org wrote:
On Mon, 2013-08-05 at 16:43 +0800, Andy Green wrote:
5) Gator bits don't seem to be in there, presumably that's something
ARM would like to see in there (it appears in llct)
Yes, and I believe someone was raising a card
On 5 August 2013 10:44, Jon Medhurst (Tixy) t...@linaro.org wrote:
On Mon, 2013-08-05 at 17:13 +0800, Andy Green wrote:
The whole list is good things to have I just wonder how ongoing
updates will be handled for backport. For example at some point
Tweaks to the MCPM code which aren't
On Mon, 2013-08-05 at 10:53 +0100, Mark Brown wrote:
On 5 August 2013 10:44, Jon Medhurst (Tixy) t...@linaro.org wrote:
On Mon, 2013-08-05 at 17:13 +0800, Andy Green wrote:
The whole list is good things to have I just wonder how
ongoing
updates
On 5 August 2013 18:00, Jon Medhurst (Tixy) t...@linaro.org wrote:
On Mon, 2013-08-05 at 10:53 +0100, Mark Brown wrote:
On 5 August 2013 10:44, Jon Medhurst (Tixy) t...@linaro.org wrote:
On Mon, 2013-08-05 at 17:13 +0800, Andy Green wrote:
The whole list is good things to
On 5 August 2013 03:45, Andy Green andy.gr...@linaro.org wrote:
1) There seems to be two choices, linux-linaro-lsk and
linux-linaro-lsk-android.
I chose the android one, I assume it has the same androidization
series on top that linux-linaro-core-tracking used at 3.10? Are there
any other
On 5 August 2013 18:16, Mark Brown broo...@linaro.org wrote:
On 5 August 2013 03:45, Andy Green andy.gr...@linaro.org wrote:
1) There seems to be two choices, linux-linaro-lsk and
linux-linaro-lsk-android.
I chose the android one, I assume it has the same androidization
series on top that
On 5 August 2013 11:00, Jon Medhurst (Tixy) t...@linaro.org wrote:
As was mentioned on linaro-kernel the plan is that you should be
sending me incremental updates as needed.
But who decides what's needed? If what is in 3.10 works, why backport a
different version? And I hadn't planned on
On Mon, Aug 05, 2013 at 06:42:33PM +0800, Andy Green wrote:
On 5 August 2013 18:16, Mark Brown broo...@linaro.org wrote:
There may be other stuff lurking in linux-linaro that I'm not aware of,
everything is supposed to be individually selected for backport.
Literally linux-linaro I'm not
On 5 August 2013 18:59, Mark Brown broo...@kernel.org wrote:
On Mon, Aug 05, 2013 at 06:42:33PM +0800, Andy Green wrote:
On 5 August 2013 18:16, Mark Brown broo...@linaro.org wrote:
There may be other stuff lurking in linux-linaro that I'm not aware of,
everything is supposed to be
On Mon, Aug 05, 2013 at 07:37:10PM +0800, Andy Green wrote:
On 5 August 2013 18:59, Mark Brown broo...@kernel.org wrote:
- The regmap change isn't something that I've seen upstream...
If you mean where did the original come from
I mean I haven't seen that warning that I'm aware of.
Hi all,
There is currently a thread on LAKML that once again touches on the
issue of automated build/boot testing:
http://permalink.gmane.org/gmane.linux.ports.arm.kernel/257669
There seemed to be some good discussions between the LAVA team and
Kevin at LCE13 and I wanted to make others are
On 08/05/2013 03:37 PM, Andy Green wrote:
On 5 August 2013 18:59, Mark Brown broo...@kernel.org wrote:
On Mon, Aug 05, 2013 at 06:42:33PM +0800, Andy Green wrote:
On 5 August 2013 18:16, Mark Brown broo...@linaro.org wrote:
There may be other stuff lurking in linux-linaro that I'm not aware
On Mon, Aug 05, 2013 at 11:23:19PM +0400, Andrey Konovalov wrote:
# Misc fixes which don't belong to any particular topic:
ynk/llct-v3.10-misc-fixes
Add cross-build support to tools/lib/lk library
perf tools: make perf to build in 3.9 kernel tree again
ARM: crypto:
On 5 August 2013 22:11, Mark Brown broo...@kernel.org wrote:
On Mon, Aug 05, 2013 at 07:37:10PM +0800, Andy Green wrote:
On 5 August 2013 18:59, Mark Brown broo...@kernel.org wrote:
- The regmap change isn't something that I've seen upstream...
If you mean where did the original come from
On 08/05/2013 05:24 PM, Andy Green wrote:
2) warning-elimination: android: binder
This seems to be a problem with a patch already upstream
3) warning-elimination: androidization: mm
Problem coming from Androidization patches
[snip]
5) warning-elimination: ion: use size_t-specific format
On 6 August 2013 11:03, John Stultz john.stu...@linaro.org wrote:
On 08/05/2013 05:24 PM, Andy Green wrote:
2) warning-elimination: android: binder
This seems to be a problem with a patch already upstream
3) warning-elimination: androidization: mm
Problem coming from Androidization
21 matches
Mail list logo
