From: "Guzman Lugo, Fernando" <fernando.lugo@ti.com>
To: "Guzman Lugo, Fernando" <fernando.lugo@ti.com>,
"Hiroshi.DOYU@nokia.com" <Hiroshi.DOYU@nokia.com>
Cc: "felipe.contreras@nokia.com" <felipe.contreras@nokia.com>,
"tony@atomide.com" <tony@atomide.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"andy.shevchenko@gmail.com" <andy.shevchenko@gmail.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: RE: [PATCHv5 0/4] iovmm: fixes for iovmm module
Date: Mon, 25 Oct 2010 13:49:04 -0500 [thread overview]
Message-ID: <496565EC904933469F292DDA3F1663E602F4936A90@dlee06.ent.ti.com> (raw)
In-Reply-To: <1288032731-541-1-git-send-email-x0095840@ti.com>
Please discard this set of patches I will send them again with
The correct prefix (omap) to avoid confusion with other
Iommu componets.
Sorry for the noise.
Regards,
Fernando.
> -----Original Message-----
> From: Guzman Lugo, Fernando
> Sent: Monday, October 25, 2010 1:52 PM
> To: Hiroshi.DOYU@nokia.com
> Cc: felipe.contreras@nokia.com; tony@atomide.com;
> linux-kernel@vger.kernel.org; andy.shevchenko@gmail.com;
> linux-omap@vger.kernel.org; Guzman Lugo, Fernando
> Subject: [PATCHv5 0/4] iovmm: fixes for iovmm module
>
> Version 5:
> * Changes in "iommu: create new api to set valid da range"
> - Change range variables to platform data structure.
>
> Version 4:
> * Changes in "iommu: create new api to set valid da range"
> - Validate range for fixed address.
> - Change way of change boundaries to avoid possible overflow
> instead of style :
> start + bytes >= end which start + end can overflow
> use style:
> end - start < bytes
>
> Version 3:
> * change patch 2 base on Felipe Contreras' comments,
> now it uses min_t and I deleted some blank lines.
> * patch "create new api to set valid da range" is base on
> "iovmm: IVA2 MMU range is from 0x11000000 to 0xFFFFFFFF"
> patch and on Hiroshi's comments and now it is added to
> this set.
>
> Version 2:
> * Removed "iovmm: fixes for iovmm module" that patch was already
> sent.
> * Modified "iovmm: fix roundup for next area and end check for the
> last area" patch, base on Davin Cohen's comments and rename it
> to a proper name that describes what it is doing now.
>
> *** BLURB HERE ***
>
> Fernando Guzman Lugo (4):
> iovmm: no gap checking for fixed address
> iovmm: add superpages support to fixed da address
> iovmm: replace __iounmap with omap_iounmap
> iommu: create new api to set valid da range
>
> arch/arm/plat-omap/include/plat/iommu.h | 3 +
> arch/arm/plat-omap/iommu.c | 33 ++++++++++++
> arch/arm/plat-omap/iovmm.c | 84
> ++++++++++++++++++-------------
> 3 files changed, 85 insertions(+), 35 deletions(-)
>
>
next prev parent reply other threads:[~2010-10-25 18:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 18:52 Fernando Guzman Lugo
2010-10-25 18:49 ` Guzman Lugo, Fernando [this message]
2010-10-25 18:52 ` [PATCHv5 1/4] iovmm: no gap checking for fixed address Fernando Guzman Lugo
2010-10-25 18:52 ` [PATCHv5 2/4] iovmm: add superpages support to fixed da address Fernando Guzman Lugo
2010-10-25 18:52 ` [PATCHv5 3/4] iovmm: replace __iounmap with omap_iounmap Fernando Guzman Lugo
2010-10-25 18:52 ` [PATCHv5 4/4] iommu: create new api to set valid da range Fernando Guzman Lugo
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=496565EC904933469F292DDA3F1663E602F4936A90@dlee06.ent.ti.com \
--to=fernando.lugo@ti.com \
--cc=Hiroshi.DOYU@nokia.com \
--cc=andy.shevchenko@gmail.com \
--cc=felipe.contreras@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--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
all inboxes | Powered by JetHome®