From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] misc omap fixes for 3.5
Date: Thu, 17 May 2012 17:00:55 -0700 [thread overview]
Message-ID: <20120518000055.GI17852@atomide.com> (raw)
In-Reply-To: <CAK=Wgbb8rXxGaSuk1VyoXz60Faek0Hd0=9EpqAAGKTt6V0FWQQ@mail.gmail.com>
* Ohad Ben-Cohen <ohad@wizery.com> [120516 02:58]:
> Hi Tony,
>
> Two important fixes from Juan that are necessary to utilize the DSP on
> OMAP4, and a trivial hwspinlock cleanup.
>
> I tried to keep things as simple as possible, but please tell me if
> you want this pull request anyway differently (e.g. split to two
> separate fixes/cleanups requests, use an annotated signed tag, etc..).
In general, yes fixes, cleanup, and devel should be all separate.
These all look like valid -rc1 fixes for me though, so pulling into
fixes-omap4-dsp branch and merging into l-o master for testing.
Regards,
Tony
> The following changes since commit d48b97b403d23f6df0b990cee652bdf9a52337a3:
>
> Linux 3.4-rc6 (2012-05-06 15:07:32 -0700)
>
> are available in the git repository at:
> git://git.kernel.org/pub/scm/linux/kernel/git/ohad/linux.git for-tony
>
> Juan Gutierrez (2):
> ARM: OMAP: enable mailbox irq per instance
> ARM: OMAP4: fix irq and clock name for dsp-iommu
>
> Ohad Ben-Cohen (1):
> ARM: OMAP4: hwspinlocks_init() should be static
>
> arch/arm/mach-omap2/hwspinlock.c | 2 +-
> arch/arm/mach-omap2/mailbox.c | 2 --
> arch/arm/mach-omap2/omap-iommu.c | 6 ++----
> arch/arm/plat-omap/mailbox.c | 13 +++++++++----
> 4 files changed, 12 insertions(+), 11 deletions(-)
>
> Thanks,
> Ohad.
prev parent reply other threads:[~2012-05-18 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 9:54 [GIT PULL] misc omap fixes for 3.5 Ohad Ben-Cohen
2012-05-18 0:00 ` 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=20120518000055.GI17852@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).