Removal of IRQF_DISABLED

Removal of IRQF_DISABLED

[Valentin Rothberg]

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

Re: Removal of IRQF_DISABLED

[Andrew Morton]

On Wed, 4 Mar 2015 10:53:07 +0100 Valentin Rothberg <valentinrothberg@gmail.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.

Re: Removal of IRQF_DISABLED

[Tony Lindgren]

* Andrew Morton <akpm@linux-foundation.org> [150304 09:46]:
> On Wed, 4 Mar 2015 10:53:07 +0100 Valentin Rothberg <valentinrothberg@gmail.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