linux-kernel - Re: [Uclinux-dist-devel] [PATCH] input/keyboard: add ADP5588 QWERTYI2C Keyboard Input device driver

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, 16 Sep 2009 00:25:56 -0400
From:	Mike Frysinger <vapier.adi@...il.com>
To:	"Song, Barry" <Barry.Song@...log.com>
Cc:	Barry Song <21cnbao@...il.com>,
	"Hennerich, Michael" <Michael.Hennerich@...log.com>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	linux-kernel@...r.kernel.org, linux-input@...r.kernel.org,
	uclinux-dist-devel@...ckfin.uclinux.org
Subject: Re: [Uclinux-dist-devel] [PATCH] input/keyboard: add ADP5588 
	QWERTYI2C Keyboard Input device driver

On Wed, Sep 16, 2009 at 00:18, Song, Barry wrote:
>From: Mike Frysinger
>>On Tue, Sep 15, 2009 at 23:49, Barry Song wrote:
>>> Even though CONFIG_GENERIC_HARDIRQS is almost always "y", in case
>>> CONFIG_GENERIC_HARDIRQS is "n" not "y", threaded_irq will become
>>> original irq, drivers will not work. So is it necessary to check the
>>> dependence of GENERIC_HARDIRQS while using threaded_irq?
>>
>>when is GENERIC_HARDIRQS not "y" ?  a quick check shows only s390/m68k
>>dont set it to "y" in their arch Kconfig ?  s390 isnt going to use any
>>of these drivers, and m68k will eventually update (m68knommu already
>>has !?).
>
> SPARC32 is "n" too. I am not caring about only these several drivers. I just want to find whether that can be a generic problem while using threaded_irq in any driver.

SPARC32 too is dead, so dont sweat it.  it's safe to assume
GENERIC_HARDIRQS is "y" in the code we write like these input drivers.
-mike
--
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/