linux-kernel - Re: [RFC] [PATCH] Fix b43 driver build for arm

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: <97a0a9ac0802212024w62dbfb03ye62c51744e853b36@mail.gmail.com>
Date:	Thu, 21 Feb 2008 21:24:32 -0700
From:	"Gordon Farquharson" <gordonfarquharson@...il.com>
To:	"Sam Ravnborg" <sam@...nborg.org>
Cc:	"Michael Buesch" <mb@...sch.de>,
	"Russell King" <rmk+lkml@....linux.org.uk>,
	linux-kernel@...r.kernel.org, linville@...driver.com,
	stefano.brivio@...imi.it, "Linus Torvalds" <torvalds@...l.org>,
	"Andrew Morton" <akpm@...l.org>, viro@....linux.org.uk
Subject: Re: [RFC] [PATCH] Fix b43 driver build for arm

Hi Sam

On Wed, Feb 20, 2008 at 12:37 PM, Sam Ravnborg <sam@...nborg.org> wrote:

>  Option 1) is the worst of the three as that can cost
>  of many hours bug-hunting.
>  Option 3) may seem optimal but I do not like to add more
>  complexity to this part of the build. And really I do not
>  know a reliable way to detech when we do cross builds anyway.
>
>  Leaving us with option 2) that is simple, strighforward and harmless.

Are you willing to sign off on and commit the patch?

Gordon

-- 
Gordon Farquharson
GnuPG Key ID: 32D6D676
--
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/