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: <CAMuHMdVV5F148RrqyGgD7q9y_C5tTnGi8S9hC4tus6wu-mLPxw@mail.gmail.com>
Date:	Sun, 30 Sep 2012 11:35:41 +0200
From:	Geert Uytterhoeven <geert@...ux-m68k.org>
To:	Jean Delvare <khali@...ux-fr.org>
Cc:	Heiko Carstens <heiko.carstens@...ibm.com>,
	Peter Huewe <peterhuewe@....de>, linux-s390@...r.kernel.org,
	Linux-Next <linux-next@...r.kernel.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [-next]: s390 *_irq() link errors

On Sun, Sep 30, 2012 at 11:20 AM, Jean Delvare <khali@...ux-fr.org> wrote:
> On Sun, 30 Sep 2012 11:08:41 +0200, Geert Uytterhoeven wrote:
>> On Sun, Sep 30, 2012 at 10:53 AM, Jean Delvare <khali@...ux-fr.org> wrote:
>> > I thought we were trying to move away from explicit arch exclusions,
>> > but if S390 is special then fine with me. I've folded Heiko's fix into
>>
>> "depends on GENERIC_HARDIRQS" is the alternative...
>
> That would make even less sense to me, I2C can work just fine without
> IRQs.

For the individual drivers that need it...

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ