All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Nishanth Menon <nm@ti.com>
Cc: Olof Johansson <olof@lixom.net>,
	arm@kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-omap@vger.kernel.org
Subject: Re: [GIT PULL 2/5] omap soc changes for v3.18 merge window
Date: Wed, 24 Sep 2014 08:46:23 -0700	[thread overview]
Message-ID: <20140924154622.GC3122@atomide.com> (raw)
In-Reply-To: <20140924152320.GA26581@kahuna>

* Nishanth Menon <nm@ti.com> [140924 08:24]:
> On 22:07-20140923, Olof Johansson wrote:
> > On Thu, Sep 11, 2014 at 04:28:55PM -0700, Tony Lindgren wrote:
> > > The following changes since commit d7eb67f7fef9c046f27a975118da2324de65a90c:
> > > 
> > >   Merge branch 'pull/v3.18/powerdomain-fixes' of https://github.com/nmenon/linux-2.6-playground into omap-for-v3.18/fixes-not-urgent (2014-09-08 15:04:24 -0700)
> > > 
> > > are available in the git repository at:
> > > 
> > >   git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/soc-for-v3.18
> > > 
> > > for you to fetch changes up to 377fb3f5d9a34b2913939e0620c1c585b5913bab:
> > > 
> > >   ARM: OMAP5+: Reuse OMAP4 PM code for OMAP5 and DRA7 (2014-09-09 19:13:41 -0700)
> > > 
> > > ----------------------------------------------------------------
> > > SoC related changes for omaps for v3.18 merge window:
> > > 
> > > - PM changes to make the code easier to use on newer SoCs
> > > - PM changes for newer SoCs suspend and resume and wake-up events
> > > - Minor clean-up to remove dead Kconfig options
> > > 
> > > Note that these have a dependency to the fixes-v3.18-not-urgent
> > > tag and is based on a commit in that series.
> > 
> > Merged. Note that this also has a fresh conflict with the latest fixes,
> > so please check that I resolved it correctly.
> > 
> 
> Looks fine to me.. also, Used a couple of out of tree patches for
> testing and all looks good from test perspective:
> 
> am335x-evm:  Boot PASS: http://slexy.org/raw/s21ul7EaiK
> am335x-sk:  Boot PASS: http://slexy.org/raw/s2xxG7b5t7
> am3517-evm:  Boot PASS: http://slexy.org/raw/s21we13Ebk
> am37x-evm:  Boot PASS: http://slexy.org/raw/s209iOnepY
> am43xx-epos:  Boot PASS: http://slexy.org/raw/s28GrriVvz
> am5728-evm:  Boot PASS: http://slexy.org/raw/s2wRllyrn2
> BeagleBoard-XM:  Boot PASS: http://slexy.org/raw/s2JPCJPebZ
> beagleboard-vanilla:  Boot PASS: http://slexy.org/raw/s2n4Pum58s
> beaglebone-black:  Boot PASS: http://slexy.org/raw/s20yDlR4eu
> craneboard:  Boot PASS: http://slexy.org/raw/s21DECJfEs
> dra72x-evm:  Boot PASS: http://slexy.org/raw/s2WgDuVxXj
> dra7xx-evm:  Boot PASS: http://slexy.org/raw/s2wOi9Okyk
> OMAP3430-Labrador(LDP):  Boot PASS: http://slexy.org/raw/s20qOiwY38
> n900:  Boot PASS: http://slexy.org/raw/s2j6hBxA2b
> omap5-evm:  Boot PASS: http://slexy.org/raw/s20Of1TCt4
> pandaboard-es:  Boot PASS: http://slexy.org/raw/s20P0IWXJX
> pandaboard-vanilla:  Boot PASS: http://slexy.org/raw/s20QWs7BP9
> sdp2430:  Boot PASS: http://slexy.org/raw/s2fXgpekEa
> sdp3430:  Boot PASS: http://slexy.org/raw/s21GW1utPn

OK thanks looks good to me also.

Regards,

Tony


WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/5] omap soc changes for v3.18 merge window
Date: Wed, 24 Sep 2014 08:46:23 -0700	[thread overview]
Message-ID: <20140924154622.GC3122@atomide.com> (raw)
In-Reply-To: <20140924152320.GA26581@kahuna>

* Nishanth Menon <nm@ti.com> [140924 08:24]:
> On 22:07-20140923, Olof Johansson wrote:
> > On Thu, Sep 11, 2014 at 04:28:55PM -0700, Tony Lindgren wrote:
> > > The following changes since commit d7eb67f7fef9c046f27a975118da2324de65a90c:
> > > 
> > >   Merge branch 'pull/v3.18/powerdomain-fixes' of https://github.com/nmenon/linux-2.6-playground into omap-for-v3.18/fixes-not-urgent (2014-09-08 15:04:24 -0700)
> > > 
> > > are available in the git repository at:
> > > 
> > >   git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/soc-for-v3.18
> > > 
> > > for you to fetch changes up to 377fb3f5d9a34b2913939e0620c1c585b5913bab:
> > > 
> > >   ARM: OMAP5+: Reuse OMAP4 PM code for OMAP5 and DRA7 (2014-09-09 19:13:41 -0700)
> > > 
> > > ----------------------------------------------------------------
> > > SoC related changes for omaps for v3.18 merge window:
> > > 
> > > - PM changes to make the code easier to use on newer SoCs
> > > - PM changes for newer SoCs suspend and resume and wake-up events
> > > - Minor clean-up to remove dead Kconfig options
> > > 
> > > Note that these have a dependency to the fixes-v3.18-not-urgent
> > > tag and is based on a commit in that series.
> > 
> > Merged. Note that this also has a fresh conflict with the latest fixes,
> > so please check that I resolved it correctly.
> > 
> 
> Looks fine to me.. also, Used a couple of out of tree patches for
> testing and all looks good from test perspective:
> 
> am335x-evm:  Boot PASS: http://slexy.org/raw/s21ul7EaiK
> am335x-sk:  Boot PASS: http://slexy.org/raw/s2xxG7b5t7
> am3517-evm:  Boot PASS: http://slexy.org/raw/s21we13Ebk
> am37x-evm:  Boot PASS: http://slexy.org/raw/s209iOnepY
> am43xx-epos:  Boot PASS: http://slexy.org/raw/s28GrriVvz
> am5728-evm:  Boot PASS: http://slexy.org/raw/s2wRllyrn2
> BeagleBoard-XM:  Boot PASS: http://slexy.org/raw/s2JPCJPebZ
> beagleboard-vanilla:  Boot PASS: http://slexy.org/raw/s2n4Pum58s
> beaglebone-black:  Boot PASS: http://slexy.org/raw/s20yDlR4eu
> craneboard:  Boot PASS: http://slexy.org/raw/s21DECJfEs
> dra72x-evm:  Boot PASS: http://slexy.org/raw/s2WgDuVxXj
> dra7xx-evm:  Boot PASS: http://slexy.org/raw/s2wOi9Okyk
> OMAP3430-Labrador(LDP):  Boot PASS: http://slexy.org/raw/s20qOiwY38
> n900:  Boot PASS: http://slexy.org/raw/s2j6hBxA2b
> omap5-evm:  Boot PASS: http://slexy.org/raw/s20Of1TCt4
> pandaboard-es:  Boot PASS: http://slexy.org/raw/s20P0IWXJX
> pandaboard-vanilla:  Boot PASS: http://slexy.org/raw/s20QWs7BP9
> sdp2430:  Boot PASS: http://slexy.org/raw/s2fXgpekEa
> sdp3430:  Boot PASS: http://slexy.org/raw/s21GW1utPn

OK thanks looks good to me also.

Regards,

Tony

  reply	other threads:[~2014-09-24 15:46 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-11 23:28 [GIT PULL 1/5] non-urgent omap fixes for v3.18 merge window Tony Lindgren
2014-09-11 23:28 ` [GIT PULL 2/5] omap soc changes " Tony Lindgren
2014-09-11 23:28 ` Tony Lindgren
2014-09-11 23:28 ` Tony Lindgren
2014-09-11 23:28 ` [GIT PULL 3/5] omap intc " Tony Lindgren
2014-09-11 23:28 ` Tony Lindgren
2014-09-11 23:28 ` Tony Lindgren
2014-09-11 23:28 ` [GIT PULL 4/5] omap mailbox " Tony Lindgren
2014-09-11 23:28 ` Tony Lindgren
2014-09-11 23:28 ` Tony Lindgren
2014-09-11 23:28 ` [GIT PULL 5/5] omap dts " Tony Lindgren
2014-09-18 20:15   ` Tony Lindgren
2014-09-18 20:15     ` Tony Lindgren
2014-09-24  5:13     ` Olof Johansson
2014-09-24  5:13       ` Olof Johansson
2014-09-11 23:28 ` Tony Lindgren
2014-09-11 23:28 ` Tony Lindgren
     [not found] ` <5412304a.04a8440a.56eb.ffff9329SMTPIN_ADDED_BROKEN@mx.google.com>
2014-09-24  5:07   ` [GIT PULL 2/5] omap soc " Olof Johansson
2014-09-24  5:07     ` Olof Johansson
2014-09-24 15:23     ` Nishanth Menon
2014-09-24 15:23       ` Nishanth Menon
2014-09-24 15:46       ` Tony Lindgren [this message]
2014-09-24 15:46         ` Tony Lindgren

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=20140924154622.GC3122@atomide.com \
    --to=tony@atomide.com \
    --cc=arm@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=olof@lixom.net \
    /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.