| 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
| ||
|
Message-ID: <1288112616-notmuch-felipe.contreras@nokia.com> Date: Tue, 26 Oct 2010 20:07:57 +0300 From: Felipe Contreras <felipe.contreras@...ia.com> To: fernando.lugo@...com, felipe.contreras@...il.com Cc: gregkh@...e.de, hiroshi.doyu@...ia.com, linux-kernel@...r.kernel.org, andy.shevchenko@...il.com, linux-omap@...r.kernel.org, linux-arm-kernel@...ts.infradead.org Subject: RE: [PATCH 1/8] staging: tidspbridge - remove req_addr from proc_map fernando.lugo@...com wrote: > > On Tue, Oct 26, 2010 at 3:51 AM, Fernando Guzman Lugo > > <x0095840@...com> wrote: > > > The device address is assigned by tidspbridge no need for > > that parameter anymore. > > > > > > Signed-off-by: Fernando Guzman Lugo <x0095840@...com> > > > > This would break the API with user-space, right? > > Yes, user-space needs to be changed accordingly. Wouldn't it make sense to avoid stuffing so many changes at once including ABI breakage? Does user-space really _needs_ to be changed? Can't you just ignore that argument? > > I think this change should be delayed, preferably after we > > have a working tidspbridge. > > The issue you were seeing must be fixed with patch 2/8, and > Having all the dependencies tidspbridge has to be working > Properly. Yes, which might not happen at .37. If we revert the iommu stuff, we might have a chance at having a working bridge on .37. -- Felipe Contreras -- 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/
Powered by blists - more mailing lists