All of lore.kernel.org
 help / color / mirror / Atom feed
From: alex.shi@linaro.org (Alex Shi)
To: linux-arm-kernel@lists.infradead.org
Subject: LSK merge linux-stable review
Date: Fri, 10 Jan 2014 23:51:30 +0800	[thread overview]
Message-ID: <52D01702.1080909@linaro.org> (raw)
In-Reply-To: <CADRr18M=sNsSD1PtoPeQw+DuQtn=p2uwFOLjEE-ztea3SnFHEQ@mail.gmail.com>

On 01/10/2014 06:41 PM, Mark Brown wrote:
> On 10 January 2014 02:58, Alex Shi <alex.shi@linaro.org
> <mailto:alex.shi@linaro.org>> wrote:
> 
>     Mark & Catalin,
> 
>     Could you like to review the merge conflict patch, which at:
>     git://git.linaro.org/kernel/linux-linaro-stable.git
>     <http://git.linaro.org/kernel/linux-linaro-stable.git>
>     linux-linaro-lsk-test
> 
> 
> This looks good (if nothing else it ends up with the same thing we have
> in mainline) providing it tests out OK.

Thanks for review. The build for -test branch is fine. guess that means
compile and reboot is fine.
But test result link still can not show test cases results. :(

https://ci.linaro.org/jenkins/job/linux-linaro-stable-lsk-pre-merge/

-- 
Thanks
    Alex

  parent reply	other threads:[~2014-01-10 15:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20140110013011.GA6447@alex-shi>
     [not found] ` <52CF61CC.40305@linaro.org>
2014-01-10 10:56   ` LSK merge linux-stable review Catalin Marinas
2014-01-10 15:31     ` Alex Shi
2014-01-10 16:32       ` Catalin Marinas
2014-01-11  1:35         ` Alex Shi
2014-01-13 15:55           ` Catalin Marinas
2014-01-14  0:32             ` Alex Shi
2014-01-14  9:45               ` Catalin Marinas
2014-01-14 10:20                 ` Alex Shi
     [not found]   ` <CADRr18M=sNsSD1PtoPeQw+DuQtn=p2uwFOLjEE-ztea3SnFHEQ@mail.gmail.com>
2014-01-10 15:51     ` Alex Shi [this message]
2014-01-10 15:53       ` Alex Shi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52D01702.1080909@linaro.org \
    --to=alex.shi@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.