| 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
| ||
|
Date: Sat, 1 Dec 2012 14:42:18 +0100 From: Daniel Vetter <daniel@...ll.ch> To: Terje Bergström <tbergstrom@...dia.com> Cc: Thierry Reding <thierry.reding@...onic-design.de>, "linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org> Subject: Re: [RFC v2 1/8] video: tegra: Add nvhost driver On Sat, Dec 1, 2012 at 12:31 PM, Terje Bergström <tbergstrom@...dia.com> wrote: > We must've talked about a bit different things. For pure register defs, > I can accommodate changing to #defines. We'd lose the code coverage > analysis, though, but if the parentheses are a make-or-break question to > upstreaming, I can change. Out of sheer curiosity: What are you using the coverage data of these register definitions for? When I looked into coverage analysis the resulting data seemed rather useless to me, since the important thing is how well we cover the entire dynamic state space of the hw+sw (e.g. crap left behind by the bios ...) and coverage seemed to be a poor proxy for that. Hence why I wonder what you're doing with this data ... -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch -- 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