From: Greg KH <greg@kroah.com>
To: Omar Ramirez Luna <omar.ramirez@ti.com>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
devel@driverdev.osuosl.org, Russell King <linux@arm.linux.org.uk>,
Tony Lindgren <tony@atomide.com>,
Felipe Contreras <felipe.contreras@gmail.com>,
linux-kernel@vger.kernel.org,
Fernando Guzman Lugo <x0095840@ti.com>,
linux-omap@vger.kernel.org, Rene Sapiens <rene.sapiens@ti.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 00/02] staging: tidspbridge: 2.6.37-rcX fixes
Date: Thu, 11 Nov 2010 05:17:56 -0800 [thread overview]
Message-ID: <20101111131756.GA26064@kroah.com> (raw)
In-Reply-To: <1289440225-27221-1-git-send-email-omar.ramirez@ti.com>
On Wed, Nov 10, 2010 at 07:50:23PM -0600, Omar Ramirez Luna wrote:
> Hi Greg,
>
> Please consider the following patch set for tidspbridge driver in
> staging tree, the following has been tested on an omap3430 based board
> + gst-dsp environment. Many thanks to Felipe Contreras for piling this up,
> as I'm just propagating his patches.
>
> First two patches:
> 1. omap: dsp: remove shm from normal memory
> 2. staging: tidspbridge: hardcode SCM macros while fix is upstreamed
>
> Resolve a couple of build breaks due to adaptations for memblock
> and SCM layer.
>
> (2) Is meant as a temporary fix, until the patches to fix this
> (currently in review) are upstreamed. [1]
>
> The rest of the series, is the revert of iommu migration changes. These
> are needed because, without modifications made to iommu module, they do not
> work; these modifications (on iommu code) didn't make it for the previous
> merge window either.
>
> I will avoid posting the reverts (unless required), they can be found
> (along with the two patches of this series) at:
>
> git://dev.omapzoom.org/pub/scm/tidspbridge/kernel-dspbridge.git
> tidspbridge-2.6.37-rc1
I've pulled from this tree and pushed it out to the staging-linus branch
to get sent to Linus before .37 is released.
thanks,
greg k-h
prev parent reply other threads:[~2010-11-11 13:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 1:50 [PATCH 00/02] staging: tidspbridge: 2.6.37-rcX fixes Omar Ramirez Luna
2010-11-11 1:50 ` [PATCH 01/02] omap: dsp: remove shm from normal memory Omar Ramirez Luna
2010-12-02 21:32 ` Russell King - ARM Linux
2010-11-11 1:50 ` [PATCH 02/02] staging: tidspbridge: hardcode SCM macros while fix is upstreamed Omar Ramirez Luna
2010-11-11 13:17 ` Greg KH [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=20101111131756.GA26064@kroah.com \
--to=greg@kroah.com \
--cc=devel@driverdev.osuosl.org \
--cc=felipe.contreras@gmail.com \
--cc=gregkh@suse.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=omar.ramirez@ti.com \
--cc=rene.sapiens@ti.com \
--cc=tony@atomide.com \
--cc=x0095840@ti.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