linux-kernel - Re: [RFC][PATCH 2/2] htirq: Allow buggy drivers of buggy hardware to write the registers.

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: <m1odrnro6l.fsf@ebiederm.dsl.xmission.com>
Date:	Sat, 04 Nov 2006 12:45:22 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	"Yinghai Lu" <yinghai.lu@....com>
Cc:	"Bryan O'Sullivan" <bos@...hscale.com>, olson@...hscale.com,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC][PATCH 2/2] htirq: Allow buggy drivers of buggy hardware to write the registers.

"Yinghai Lu" <yinghai.lu@....com> writes:

> why not create one standard update function. and use that us default
> for cfg->update

It is faster and clearer what the normal case is not to have an update
function.  In practice I only ever expect one card to actually use the
update function.

Eric
-
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/