On Fri, Jun 13, 2014 at 3:28 PM, Joseph Salisbury
<email address hidden> wrote:
> Just to confirm this commit fixes this bug, I built a Trusty test kernel, which can be downloaded from:
> http://kernel.ubuntu.com/~jsalisbury/lp1328295/
>
> Can you test this kernel to confirm it fixes this bug?
My target platform is arm64 - if you can provide arm64 binaries, or
the source, I could test it. Though, I have already tested a trusty
kernel with this cherry-pick on the target platform.
> If it does, we
> can submit an SRU request to the kernel-team mailing list to have the
> commit included in Trusty.
On Fri, Jun 13, 2014 at 3:28 PM, Joseph Salisbury kernel. ubuntu. com/~jsalisbury /lp1328295/
<email address hidden> wrote:
> Just to confirm this commit fixes this bug, I built a Trusty test kernel, which can be downloaded from:
> http://
>
> Can you test this kernel to confirm it fixes this bug?
My target platform is arm64 - if you can provide arm64 binaries, or
the source, I could test it. Though, I have already tested a trusty
kernel with this cherry-pick on the target platform.
> If it does, we
> can submit an SRU request to the kernel-team mailing list to have the
> commit included in Trusty.
This commit is already in the master-next branch for trusty: kernel. ubuntu. com/git? p=ubuntu/ ubuntu- trusty. git;a=commit; h=3545bd96109d7 6abb535f2751cb7 162bc519a11a
http://
Based on this request: /lists. ubuntu. com/archives/ kernel- team/2014- June/043580. html
https:/
Does that imply we're good?