From: Tony Lindgren <tony@atomide.com>
To: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: [GIT PULL] few omap fixups for v3.5 merge window
Date: Fri, 11 May 2012 12:22:31 -0700 [thread overview]
Message-ID: <20120511192230.GV21851@atomide.com> (raw)
Hi Arnd & Olof,
Here are the fixes needed for the regressions caused by
omap-cleanup-sparse-for-v3.5. I suggest pulling this into
arm-soc/omap/cleanup-sparse where the issues got introduced.
Regards,
Tony
The following changes since commit 09f45b83109cb8e23a06d5efb1096a08a9545974:
Merge tag 'omap-cleanup-a2-for-3.5' of git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending into cleanup-sparse (2012-04-18 10:09:26 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap fixes-for-cleanup
for you to fetch changes up to 19b08b33fa4c60d66d4e341d4d1d9a6e86ffc9e6:
ARM: OMAP: OTG integration: fix compiler warning (2012-05-11 09:56:43 -0700)
----------------------------------------------------------------
Turns out the earlier omap-cleanup-sparse-for-v3.5
up introduced one compile issue and a new warning.
----------------------------------------------------------------
Paul Walmsley (2):
ARM: OMAP1: USB: fix ocpi_enable compile problem on non-1610 builds
ARM: OMAP: OTG integration: fix compiler warning
arch/arm/mach-omap1/common.h | 4 ++++
arch/arm/plat-omap/usb.c | 4 +++-
2 files changed, 7 insertions(+), 1 deletion(-)
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] few omap fixups for v3.5 merge window
Date: Fri, 11 May 2012 12:22:31 -0700 [thread overview]
Message-ID: <20120511192230.GV21851@atomide.com> (raw)
Hi Arnd & Olof,
Here are the fixes needed for the regressions caused by
omap-cleanup-sparse-for-v3.5. I suggest pulling this into
arm-soc/omap/cleanup-sparse where the issues got introduced.
Regards,
Tony
The following changes since commit 09f45b83109cb8e23a06d5efb1096a08a9545974:
Merge tag 'omap-cleanup-a2-for-3.5' of git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending into cleanup-sparse (2012-04-18 10:09:26 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap fixes-for-cleanup
for you to fetch changes up to 19b08b33fa4c60d66d4e341d4d1d9a6e86ffc9e6:
ARM: OMAP: OTG integration: fix compiler warning (2012-05-11 09:56:43 -0700)
----------------------------------------------------------------
Turns out the earlier omap-cleanup-sparse-for-v3.5
up introduced one compile issue and a new warning.
----------------------------------------------------------------
Paul Walmsley (2):
ARM: OMAP1: USB: fix ocpi_enable compile problem on non-1610 builds
ARM: OMAP: OTG integration: fix compiler warning
arch/arm/mach-omap1/common.h | 4 ++++
arch/arm/plat-omap/usb.c | 4 +++-
2 files changed, 7 insertions(+), 1 deletion(-)
next reply other threads:[~2012-05-11 19:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 19:22 Tony Lindgren [this message]
2012-05-11 19:22 ` [GIT PULL] few omap fixups for v3.5 merge window Tony Lindgren
2012-05-12 5:22 ` Olof Johansson
2012-05-12 5:22 ` Olof Johansson
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=20120511192230.GV21851@atomide.com \
--to=tony@atomide.com \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--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.