linux-kernel - Re: [GIT PULL] fixes for tidspbridge 2.6.37-rc1

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: <AANLkTinLORQ7Hyn7nqkNZhRbP8iTGRfAXibgY2VeZTPq@mail.gmail.com>
Date:	Tue, 9 Nov 2010 11:52:17 -0600
From:	"Guzman Lugo, Fernando" <fernando.lugo@...com>
To:	Tony Lindgren <tony@...mide.com>
Cc:	Arnd Bergmann <arnd@...db.de>,
	Felipe Contreras <felipe.contreras@...il.com>,
	Greg KH <greg@...ah.com>, linux-omap@...r.kernel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Omar Ramirez Luna <omar.ramirez@...com>
Subject: Re: [GIT PULL] fixes for tidspbridge 2.6.37-rc1

On Tue, Nov 9, 2010 at 11:35 AM, Tony Lindgren <tony@...mide.com> wrote:
> * Guzman Lugo, Fernando <fernando.lugo@...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?

Here are the missing patches:

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

and
  scatterlist: define SG chain for arm architecture


Regards,
Fernando.



>
> That way we can at least start merging those into linux-omap for
> testing while waiting for the next merge window.
>
> Tony
>
--
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/