From: Greg KH <greg@kroah.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Felipe Contreras <felipe.contreras@gmail.com>,
linux-omap@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Omar Ramirez Luna <omar.ramirez@ti.com>,
Fernando Guzman Lugo <fernando.lugo@ti.com>,
Tony Lindgren <tony@atomide.com>
Subject: Re: [GIT PULL] fixes for tidspbridge 2.6.37-rc1
Date: Tue, 9 Nov 2010 08:55:09 -0800 [thread overview]
Message-ID: <20101109165509.GA9698@kroah.com> (raw)
In-Reply-To: <201011091729.17679.arnd@arndb.de>
On Tue, Nov 09, 2010 at 05:29:17PM +0100, Arnd Bergmann wrote:
> On Tuesday 09 November 2010, Felipe Contreras wrote:
> > Felipe Contreras (14):
> > Revert "staging: tidspbridge - update Kconfig to select IOMMU module"
> > Revert "staging: tidspbridge - remove dmm custom module"
> > Revert "staging: tidspbridge - deprecate reserve/unreserve_memory funtions"
> > Revert "staging: tidspbridge - remove reserved memory clean up"
> > Revert "staging: tidspbridge: remove dw_dmmu_base from cfg_hostres struct"
> > Revert "staging: tidspbridge - move all iommu related code to a new file"
> > Revert "staging: tidspbridge - remove hw directory"
> > Revert "staging: tidspbridge - fix mmufault support"
> > Revert "staging: tidspbridge - remove custom mmu code from tiomap3430.c"
> > Revert "staging: tidspbridge - rename bridge_brd_mem_map/unmap to a proper name"
> > Revert "staging: tidspbridge - move shared memory iommu maps to tiomap3430.c"
> > Revert "staging: tidspbridge: replace iommu custom for opensource implementation"
>
> That adds quite a lot of crap back in that was removed by Fernando earlier:
>
> 44 files changed, 3733 insertions(+), 847 deletions(-)
>
> It may have been premature to merge the patches as you say, but now that
> they are in, I'd vote for giving Fernando a chance to fix up any damage
> that was done in the process rather than just reverting all the useful
> changes.
In looking at this further, I agree.
Felipe, are all of these really needing to be reverted? How about
picking out the functional changes that need to be resolved instead of
just rolling back everything that has been done here. Surely not all of
these are wrong, right?
thanks,
greg k-h
next prev parent reply other threads:[~2010-11-09 16:58 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
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 [this message]
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=20101109165509.GA9698@kroah.com \
--to=greg@kroah.com \
--cc=arnd@arndb.de \
--cc=felipe.contreras@gmail.com \
--cc=fernando.lugo@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--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