From: Greg KH <greg@kroah.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
linux-main <linux-kernel@vger.kernel.org>,
Ohad Ben-Cohen <ohad@wizery.com>,
Tony Lindgren <tony@atomide.com>,
Omar Ramirez Luna <omar.ramirez@ti.com>,
Hiroshi Doyu <hiroshi.doyu@nokia.com>
Subject: Re: [PATCH 0/2] omap: dsp: make the driver actually work
Date: Tue, 5 Oct 2010 12:07:41 -0700 [thread overview]
Message-ID: <20101005190741.GC20825@kroah.com> (raw)
In-Reply-To: <1286208555-8829-1-git-send-email-felipe.contreras@gmail.com>
On Mon, Oct 04, 2010 at 07:09:13PM +0300, Felipe Contreras wrote:
> Hi,
>
> It seems the platform device was dropped from the migration of tidspbridge into
> staging, plus the sdram meblock (previously bootmem) required for it work are
> gone.
>
> Withouth these patches the driver loads, but doesn't do anything.
>
> A second issue with ioremap() still remains, but that can be solved by
> reverting 309caa9.
>
> I think these might be worth to get into 2.6.36, if not, I have versions with
> more changes; cleanups and so on.
I've applied this to my staging-next tree, for .37, as it's not a big
deal for .36.
thanks,
greg k-h
next prev parent reply other threads:[~2010-10-05 19:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 16:09 [PATCH 0/2] omap: dsp: make the driver actually work Felipe Contreras
2010-10-04 16:09 ` [PATCH 1/2] omap: add dsp platform device Felipe Contreras
2010-10-05 15:56 ` Greg KH
2010-10-05 16:28 ` Tony Lindgren
2010-10-05 19:04 ` Greg KH
2010-10-04 16:09 ` [PATCH 2/2] staging: tidspbridge: use omap_dsp_platform_data Felipe Contreras
2010-10-05 19:07 ` Greg KH [this message]
2010-10-05 19:23 ` [PATCH 0/2] omap: dsp: make the driver actually work Felipe Contreras
2010-10-05 19:52 ` Ramirez Luna, Omar
2010-10-05 20:02 ` Felipe Contreras
2010-10-05 20:09 ` Ramirez Luna, Omar
2010-10-05 21:05 ` Felipe Contreras
2010-10-07 1:32 ` Omar Ramirez Luna
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=20101005190741.GC20825@kroah.com \
--to=greg@kroah.com \
--cc=felipe.contreras@gmail.com \
--cc=hiroshi.doyu@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=omar.ramirez@ti.com \
--cc=tony@atomide.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).