From: Tony Lindgren <tony@atomide.com>
To: "Guzman Lugo, Fernando" <fernando.lugo@ti.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Felipe Contreras <felipe.contreras@gmail.com>,
Greg KH <greg@kroah.com>,
linux-omap@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Omar Ramirez Luna <omar.ramirez@ti.com>
Subject: Re: [GIT PULL] fixes for tidspbridge 2.6.37-rc1
Date: Tue, 9 Nov 2010 09:35:36 -0800 [thread overview]
Message-ID: <20101109173536.GE9264@atomide.com> (raw)
In-Reply-To: <AANLkTikMjAh+LAFaWELyiJc+ou+N8v_7xhrwHRbBZZQF@mail.gmail.com>
* Guzman Lugo, Fernando <fernando.lugo@ti.com> [101109 08:36]:
>
> tidspbridge iommu change are working fine all the patches and few fixes after
> that are alredy sent. what breaks tidspbridge, is the unmerged
> dependencies in linux omap tree, specifically the iommu module patches
> and the SG patch.
Care to post a series of the missing patches listed above?
That way we can at least start merging those into linux-omap for
testing while waiting for the next merge window.
Tony
next prev parent reply other threads:[~2010-11-09 17:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-07 21:36 [GIT PULL] fixes for tidspbridge 2.6.37-rc1 Felipe Contreras
2010-11-08 23:00 ` Felipe Contreras
2010-11-09 0:57 ` Tony Lindgren
2010-11-09 16:29 ` Arnd Bergmann
2010-11-09 16:46 ` Guzman Lugo, Fernando
2010-11-09 17:35 ` Tony Lindgren [this message]
2010-11-09 17:52 ` Guzman Lugo, Fernando
2010-11-09 18:32 ` Tony Lindgren
2010-11-09 22:13 ` Felipe Contreras
2010-11-09 21:26 ` Felipe Contreras
2010-11-09 16:55 ` Greg KH
2010-11-09 17:04 ` Guzman Lugo, Fernando
2010-11-09 17:25 ` Greg KH
2010-11-09 17:49 ` Guzman Lugo, Fernando
2010-11-09 17:58 ` Greg KH
2010-11-09 18:40 ` Ramirez Luna, Omar
2010-11-09 21:53 ` Felipe Contreras
2010-11-09 22:10 ` Greg KH
2010-11-09 22:39 ` Felipe Contreras
2010-11-09 22:52 ` Greg KH
2010-11-09 22:04 ` Felipe Contreras
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=20101109173536.GE9264@atomide.com \
--to=tony@atomide.com \
--cc=arnd@arndb.de \
--cc=felipe.contreras@gmail.com \
--cc=fernando.lugo@ti.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=omar.ramirez@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