linux-omap.vger.kernel.org archive mirror
 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: fix build, sparse problems in cleanup-headers
Date: Fri, 26 Oct 2012 13:19:43 -0700	[thread overview]
Message-ID: <20121026201943.GS11908@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1210262012250.11258@utopia.booyaka.com>

* Paul Walmsley <paul@pwsan.com> [121026 13:16]:
> Hi Tony,
> 
> The following changes since commit 2da8a79f7d81853d00b6a00621aeef7545196084:
> 
>   Merge branch 'omap-for-v3.8/cleanup-headers-menelaus' into omap-for-v3.8/cleanup-headers (2012-10-25 12:21:48 -0700)
> 
> are available in the git repository at:
> 
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git tags/omap-cleanup-fixes-a-for-3.8
> 
> for you to fetch changes up to 97af08b6e10e06563309728ed2fe8fdd919c5a33:
> 
>   ARM: OMAP1: fix sparse warning added by commit 4c98dc6b8ef2f73bdbfa78186db9a76507ba9ea3 (2012-10-26 13:21:48 -0600)
> 
> ----------------------------------------------------------------
> Several fixes for build failures and sparse warnings in the
> OMAP cleanup-headers branch.  Intended for 3.8 cleanup.
> 
> Basic build, boot, and PM test logs are available from here:
> 
>     http://www.pwsan.com/omap/testlogs/cleanup-headers-compile-fixes-3.8/20121026132711/
> 
> Due to underlying problems in v3.7-rc2, several tests fail.  These
> failures are unrelated to these patches.

Thanks pulling into omap-for-v3.8/cleanup-headers.

Regards,

Tony
 
> ----------------------------------------------------------------
> Paul Walmsley (3):
>       ARM: OMAP2+: fix build breakage introduced by commit b7754452b3e27716347a528b47b0a1083af32520
>       ARM: OMAP1: fix build breakage introduced by commit 25c7d49ed48b4843da7dea56a81ae7f620211ee0
>       ARM: OMAP1: fix sparse warning added by commit 4c98dc6b8ef2f73bdbfa78186db9a76507ba9ea3
> 
>  arch/arm/mach-omap1/fpga.c   |    1 +
>  arch/arm/mach-omap1/pm_bus.c |    2 ++
>  drivers/mtd/onenand/omap2.c  |   36 ++++++++++++++++++++++++------------
>  3 files changed, 27 insertions(+), 12 deletions(-)
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2012-10-26 20:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-26 20:14 [GIT PULL] ARM: OMAP: fix build, sparse problems in cleanup-headers Paul Walmsley
2012-10-26 20:19 ` Tony Lindgren [this message]

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=20121026201943.GS11908@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).