linux-kernel - Removal of IRQF

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAD3Xx4Kwsb-0=fBZr8s6BkFdJDZF+nkAbkYVuJMCrCb03Uzv2Q@mail.gmail.com>
Date:	Wed, 4 Mar 2015 10:53:07 +0100
From:	Valentin Rothberg <valentinrothberg@...il.com>
To:	tony@...mide.com, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org
Subject: Removal of IRQF_DISABLED

Hi,

Andrew asked me to prepare one big patch that removes the
IRQF_DISABLED flag entirely.  I already sent a few small patches that
remove the usage of this flag,  two of them [1, 2] have been applied
by Tony to omap-for-v4.1/l3.  Hence, I cannot remove the definition
now and leave the files of [1, 2] untouched.

I don't want to break anything or cause troubles while merging.  So
shall I wait until v4.1 to send the big patch or is there are nice way
to get it merged now (e.g., getting [1, 2] into omap-for-v4.0)?

Kind regards,
 Valentin

[1] https://lkml.org/lkml/2015/3/2/306
[2] https://lkml.org/lkml/2015/3/2/492
--
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/