From: Greg KH <greg@kroah.com>
To: Fernando Guzman Lugo <x0095840@ti.com>
Cc: gregkh@suse.de, felipe.contreras@nokia.com,
ameya.palande@nokia.com, nm@ti.com, Hiroshi.DOYU@nokia.com,
ohad@wizery.com, linux-kernel@vger.kernel.org,
andy.shevchenko@gmail.com, linux-omap@vger.kernel.org
Subject: Re: [PATCHv2 01/11] staging: tidspbridge: replace iommu custom for opensource implementation
Date: Tue, 5 Oct 2010 08:55:41 -0700 [thread overview]
Message-ID: <20101005155541.GA24456@kroah.com> (raw)
In-Reply-To: <1285899178-14413-2-git-send-email-x0095840@ti.com>
On Thu, Sep 30, 2010 at 09:12:48PM -0500, Fernando Guzman Lugo wrote:
> Now the tidspbridge uses the API's from
> iovmm module.
>
> Signed-off-by: Fernando Guzman Lugo <x0095840@ti.com>
This patch applied, but number 2 and others didn't. Care to respin
those against the new linux-next tree and resend?
thanks,
greg k-h
next prev parent reply other threads:[~2010-10-05 16:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-01 2:12 [PATCHv2 00/11] staging tidspbridge: iommu migration Fernando Guzman Lugo
2010-10-01 2:12 ` Fernando Guzman Lugo
2010-10-01 2:12 ` [PATCHv2 01/11] staging: tidspbridge: replace iommu custom for opensource implementation Fernando Guzman Lugo
2010-10-01 2:12 ` Fernando Guzman Lugo
2010-10-01 2:12 ` [PATCHv2 02/11] staging: tidspbridge - move shared memory iommu maps to tiomap3430.c Fernando Guzman Lugo
2010-10-01 2:12 ` Fernando Guzman Lugo
2010-10-01 2:12 ` [PATCHv2 03/11] staging: tidspbridge - rename bridge_brd_mem_map/unmap to a proper name Fernando Guzman Lugo
2010-10-01 2:12 ` Fernando Guzman Lugo
2010-10-01 2:12 ` [PATCHv2 04/11] staging: tidspbridge - remove custom mmu code from tiomap3430.c Fernando Guzman Lugo
2010-10-01 2:12 ` Fernando Guzman Lugo
2010-10-01 2:12 ` [PATCHv2 05/11] staging: tidspbridge - fix mmufault support Fernando Guzman Lugo
2010-10-01 2:12 ` Fernando Guzman Lugo
2010-10-01 2:12 ` [PATCHv2 06/11] staging: tidspbrge - remove hw directory Fernando Guzman Lugo
2010-10-01 2:12 ` Fernando Guzman Lugo
2010-10-01 2:12 ` [PATCHv2 07/11] staging: tidspbridge - move all iommu related code to a new file Fernando Guzman Lugo
2010-10-01 2:12 ` Fernando Guzman Lugo
2010-10-01 2:12 ` [PATCHv2 08/11] staging: tidspbridge: remove dw_dmmu_base from cfg_hostres struct Fernando Guzman Lugo
2010-10-01 2:12 ` Fernando Guzman Lugo
2010-10-01 2:12 ` [PATCHv2 09/11] staging: tidspbridge - remove reserved memory clean up Fernando Guzman Lugo
2010-10-01 2:12 ` Fernando Guzman Lugo
2010-10-01 2:12 ` [PATCHv2 10/11] staging: tidspbridge - deprecate reserve/unreserve_memory funtions Fernando Guzman Lugo
2010-10-01 2:12 ` Fernando Guzman Lugo
2010-10-01 2:12 ` [PATCHv2 11/11] staging: tidspbridge - remove dmm custom module Fernando Guzman Lugo
2010-10-01 2:12 ` Fernando Guzman Lugo
2010-10-05 15:55 ` Greg KH [this message]
2010-10-05 17:47 ` [PATCHv2 01/11] staging: tidspbridge: replace iommu custom for opensource implementation Guzman Lugo, Fernando
2010-10-05 20:30 ` Guzman Lugo, Fernando
2010-10-04 15:36 ` [PATCHv2 00/11] staging tidspbridge: iommu migration 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=20101005155541.GA24456@kroah.com \
--to=greg@kroah.com \
--cc=Hiroshi.DOYU@nokia.com \
--cc=ameya.palande@nokia.com \
--cc=andy.shevchenko@gmail.com \
--cc=felipe.contreras@nokia.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=ohad@wizery.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.