linux-kernel - Re: [PATCHv7 0/4] omap: iovmm

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <AANLkTi=CCVe0ST0UiwMrfy8RsP-xfS9gCxUewv1q5Vu=@mail.gmail.com>
Date:	Tue, 14 Dec 2010 19:54:17 -0600
From:	"Kanigeri, Hari" <h-kanigeri2@...com>
To:	Fernando Guzman Lugo <fernando.lugo@...com>
Cc:	Hiroshi.DOYU@...ia.com, linux@....linux.org.uk,
	linux-kernel@...r.kernel.org, linux-omap@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, tony@...mide.com
Subject: Re: [PATCHv7 0/4] omap: iovmm - fixes for iovmm module

Fernando,

For omap patches, follow the convention

OMAP: iommu: <subject>
OMAP: iovmm: <subject>

Ref: http://www.spinics.net/lists/linux-omap/msg39956.html


On Tue, Dec 14, 2010 at 6:53 PM, Fernando Guzman Lugo
<fernando.lugo@...com> wrote:
> Misc fixes found while working with iovmm module. They are
> needed in order to tidspbridge can work properly along with
> iovmm module.
>
> Version 7:
> * Change 4/4 patch base on Felipe Contreras comments about
>  having start/end in platform data and struct iommu.
>
> Version 6:
> * Rebase on Russell King branch.
>  - for details see:
>  http://marc.info/?l=linux-omap&m=129228495723001&w=2
>
> 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.
>
>
> Guzman Lugo, Fernando (4):
>  omap: iovmm - no gap checking for fixed address
>  omap: iovmm - add superpages support to fixed da address
>  omap: iovmm - replace __iounmap with iounmap
>  omap: iommu - create new api to set valid da range
>
>  arch/arm/mach-omap2/omap-iommu.c        |    8 +++
>  arch/arm/plat-omap/include/plat/iommu.h |    5 ++
>  arch/arm/plat-omap/iommu.c              |   24 +++++++++
>  arch/arm/plat-omap/iovmm.c              |   81 +++++++++++++++++-------------
>  4 files changed, 83 insertions(+), 35 deletions(-)
>
>



-- 
Thank you,
Best regards,
Hari Kanigeri
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/