S390: Upstream changes from the past 2 weeks

S390: Upstream changes from the past 2 weeks

Upstream S390 platform specific code to latest lkgr from the past 2 weeks.

R=danno@chromium.org,jkummerow@chromium.org,jochen@chromium.org,joransiu@ca.ibm.com,michael_dawson@ca.ibm.com,mbrandy@us.ibm.com
BUG=

Committed: https://crrev.com/5f5988299a8e1870fbf294f50a97770b00c272bd
Cr-Commit-Position: refs/heads/master@{#34787}

[john.yan, 2016-03-14 21:49:47]

Upstream S390 platform specific code to latest lkgr from the past 2 weeks. 
Moving forward, we will be porting individual specific commits that require
platform changes

[Yang, 2016-03-15 07:58:55]

On 2016/03/14 21:49:47, john.yan wrote:
> Upstream S390 platform specific code to latest lkgr from the past 2 weeks. 
> Moving forward, we will be porting individual specific commits that require
> platform changes

src/debug and src/full-codegen lgtm.

[Jakob Kummerow, 2016-03-15 08:59:27]

jkummerow@chromium.org changed reviewers:
+ mstarzinger@chromium.org

[Jakob Kummerow, 2016-03-15 08:59:28]

rubberstamp LGTM on *-s390.{h,cc}.

This still needs an OWNERS stamp for src/compiler/. Michi?

S390 team: if you had OWNERS files for all the */s390/ directories already, you
could have just landed this yourselves ;-)

[Michael Starzinger, 2016-03-15 09:01:33]

LGTM (rubber-stamp of compiler).

[john.yan, 2016-03-15 12:53:55]

The CQ bit was checked by jyan@ca.ibm.com

[commit-bot: I haz the power, 2016-03-15 12:54:10]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1799893002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1799893002/1

[john.yan, 2016-03-15 12:58:06]

On 2016/03/15 08:59:28, Jakob wrote:
> rubberstamp LGTM on *-s390.{h,cc}.
> 
> This still needs an OWNERS stamp for src/compiler/. Michi?
> 
> S390 team: if you had OWNERS files for all the */s390/ directories already,
you
> could have just landed this yourselves ;-)

Thanks Jakob. Do we need any approve to check in OWERS file? or we can just add
it by ourself?

[Jakob Kummerow, 2016-03-15 13:03:38]

On 2016/03/15 12:58:06, john.yan wrote:
> Thanks Jakob. Do we need any approve to check in OWERS file? or we can just
add
> it by ourself?

For the CL that adds OWNERS files itself you'll still need reviews just like
here; but after that you can review changes within those directories yourselves.
There is no formal approval/nomination/discussion process for deciding whether
or not you should be OWNERS: since you're maintaining the s390 port, you should
be its OWNERS. Just like it's already the case for PPC.

[commit-bot: I haz the power, 2016-03-15 13:12:51]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-03-15 13:14:28]

Description was changed from

==========
S390: Upstream changes from the past 2 weeks

Upstream S390 platform specific code to latest lkgr from the past 2 weeks.

R=danno@chromium.org,jkummerow@chromium.org,jochen@chromium.org,joransiu@ca.i...
BUG=
==========

to

==========
S390: Upstream changes from the past 2 weeks

Upstream S390 platform specific code to latest lkgr from the past 2 weeks.

R=danno@chromium.org,jkummerow@chromium.org,jochen@chromium.org,joransiu@ca.i...
BUG=

Committed: https://crrev.com/5f5988299a8e1870fbf294f50a97770b00c272bd
Cr-Commit-Position: refs/heads/master@{#34787}
==========

[commit-bot: I haz the power, 2016-03-15 13:14:29]

Patchset 1 (id:??) landed as
https://crrev.com/5f5988299a8e1870fbf294f50a97770b00c272bd
Cr-Commit-Position: refs/heads/master@{#34787}