linux-kernel - Re: 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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Wed, 4 Mar 2015 11:02:09 -0800
From:	Tony Lindgren <tony@...mide.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Valentin Rothberg <valentinrothberg@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: Removal of IRQF_DISABLED

* Andrew Morton <akpm@...ux-foundation.org> [150304 09:46]:
> On Wed, 4 Mar 2015 10:53:07 +0100 Valentin Rothberg <valentinrothberg@...il.com> wrote:
> 
> > 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)?
> > 
> 
> You're over-sweating this - merging patches is what we do ;)
> 
> Just send the patch, against current Linus mainline and I'll work it
> out.

Yeah and I'll drop my omap-for-v4.1/l3 branch no problem. I don't yet
have anything applied on top of those two patches.

Regards,

Tony
--
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/