Re: [GIT PULL] ARM: OMAP: clock, powerdomain, clockdomain, hwmod fixes for early v3.4-rc

All of lore.kernel.org
 help / color / mirror / Atom feed

From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] ARM: OMAP: clock, powerdomain, clockdomain, hwmod fixes for early v3.4-rc
Date: Wed, 4 Apr 2012 17:41:40 -0700	[thread overview]
Message-ID: <20120405004139.GA10780@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1204041658200.7161@utopia.booyaka.com>

* Paul Walmsley <paul@pwsan.com> [120404 16:03]:
> Hi Tony,
> 
> The following changes since commit dd775ae2549217d3ae09363e3edb305d0fa19928:
> 
>   Linux 3.4-rc1 (2012-03-31 16:24:09 -0700)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending tags/omap-fixes-a-for-3.4rc
> 
> for you to fetch changes up to cf1a9298231d7719b67ad0eae6236c91888b7a32:
> 
>   Merge branches 'clock_fixes_3.4rc', 'clockdomain_fixes_3.4rc', 'hsmmc_erratum_2_1_1_128_refine_3.4rc1', 'hwmod_data_fixes_a_3.4rc', 'hwmod_fixes_3.4rc', 'powerdomain_fixes_a_3.4rc' and 'prcm_fixes_3.4rc' into fixes_for_3.4rc2 (2012-04-04 14:53:33 -0600)
> 
> These changes have been boot-tested on OMAP37xx ES1.0 Beagleboard-XM,
> OMAP2420 N800, OMAP4430 ES2.0 Pandaboard, and OMAP35xx ES3.0
> BeagleBoard.  System suspend and serial wakeup has been tested
> on OMAP4430 ES2.0 Pandaboard, and dynamic retention idle and serial
> wakeup has been tested on OMAP35xx ES3.0 BeagleBoard.

Thanks, looks like two of these patches I already merged into
fixes yesterday from your earlier pull request. So merging this
in would cause duplicate commits. Can you please update your
branch to remove those two commits?

Meanwhile, I've merged your branch into linux-omap master branch
for some more testing while waiting for the update.

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] ARM: OMAP: clock, powerdomain, clockdomain, hwmod fixes for early v3.4-rc
Date: Wed, 4 Apr 2012 17:41:40 -0700	[thread overview]
Message-ID: <20120405004139.GA10780@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1204041658200.7161@utopia.booyaka.com>

* Paul Walmsley <paul@pwsan.com> [120404 16:03]:
> Hi Tony,
> 
> The following changes since commit dd775ae2549217d3ae09363e3edb305d0fa19928:
> 
>   Linux 3.4-rc1 (2012-03-31 16:24:09 -0700)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending tags/omap-fixes-a-for-3.4rc
> 
> for you to fetch changes up to cf1a9298231d7719b67ad0eae6236c91888b7a32:
> 
>   Merge branches 'clock_fixes_3.4rc', 'clockdomain_fixes_3.4rc', 'hsmmc_erratum_2_1_1_128_refine_3.4rc1', 'hwmod_data_fixes_a_3.4rc', 'hwmod_fixes_3.4rc', 'powerdomain_fixes_a_3.4rc' and 'prcm_fixes_3.4rc' into fixes_for_3.4rc2 (2012-04-04 14:53:33 -0600)
> 
> These changes have been boot-tested on OMAP37xx ES1.0 Beagleboard-XM,
> OMAP2420 N800, OMAP4430 ES2.0 Pandaboard, and OMAP35xx ES3.0
> BeagleBoard.  System suspend and serial wakeup has been tested
> on OMAP4430 ES2.0 Pandaboard, and dynamic retention idle and serial
> wakeup has been tested on OMAP35xx ES3.0 BeagleBoard.

Thanks, looks like two of these patches I already merged into
fixes yesterday from your earlier pull request. So merging this
in would cause duplicate commits. Can you please update your
branch to remove those two commits?

Meanwhile, I've merged your branch into linux-omap master branch
for some more testing while waiting for the update.

Regards,

Tony

next prev parent reply	other threads:[~2012-04-05  0:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-04 23:00 [GIT PULL] ARM: OMAP: clock, powerdomain, clockdomain, hwmod fixes for early v3.4-rc Paul Walmsley
2012-04-04 23:00 ` Paul Walmsley
2012-04-05  0:41 ` Tony Lindgren [this message]
2012-04-05  0:41   ` Tony Lindgren
2012-04-05  2:07   ` Paul Walmsley
2012-04-05  2:07     ` Paul Walmsley
2012-04-05  8:50     ` Paul Walmsley
2012-04-05  8:50       ` Paul Walmsley
2012-04-05 16:42       ` Tony Lindgren
2012-04-05 16:42         ` Tony Lindgren
2012-04-05 19:50         ` Paul Walmsley
2012-04-05 19:50           ` Paul Walmsley
2012-04-05  9:06 ` Madhusudhan.Gowda
2012-04-05  9:06   ` Madhusudhan.Gowda at elektrobit.com
2012-04-05  9:19   ` Paul Walmsley
2012-04-05  9:19     ` Paul Walmsley
2012-04-05  9:40     ` Madhusudhan.Gowda
2012-04-05  9:40       ` Madhusudhan.Gowda at elektrobit.com
2012-06-22 14:48       ` Paul Walmsley
2012-06-22 14:48         ` Paul Walmsley

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=20120405004139.GA10780@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    /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.