linux-kernel - Re: [PATCH] IB/ipath - program intconfig register using new HT irq hook

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]

Date:	Wed, 8 Nov 2006 15:18:21 -0800
From:	Andrew Morton <akpm@...l.org>
To:	"Bryan O'Sullivan" <bos@...hscale.com>
Cc:	rdreier@...co.com, ebiederm@...ssion.com,
	linux-kernel@...r.kernel.org, openib-general@...nib.org
Subject: Re: [PATCH] IB/ipath - program intconfig register using new HT irq
 hook

On Wed, 08 Nov 2006 15:08:30 -0800
"Bryan O'Sullivan" <bos@...hscale.com> wrote:

> Andrew Morton wrote:
> 
> > so...  Is this:
> > 
> > htirq-refactor-so-we-only-have-one-function-that-writes-to-the-chip.patch
> > htirq-allow-buggy-drivers-of-buggy-hardware-to-write-the-registers.patch
> 
> You should drop the above patch from Eric...
> 
> > htirq-allow-buggy-drivers-of-buggy-hardware-to-write-the-registers-update.patch
> 
> ...in favour of this one, which is my rework of Eric's patch.
> 
> > ib-ipath-program-intconfig-register-using-new-ht-irq-hook.patch

If you look, you'll see that the
htirq-allow-buggy-drivers-of-buggy-hardware-to-write-the-registers-update.patch
which I merged is the diff between Eric's patch and yours (ie: the diff
which you should have sent ;))

> > considered 2.6.19 material?
> 
> Yes, please.  I might be able to simplify the ib-ipath patch (by a 
> matter of a few lines), but it works fine as it stands.
> 

ho hum, OK.
-
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/