linux-kernel - Re: linux-next: build failure after merge of the staging tree

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20201207204515.617298c5@canb.auug.org.au>
Date:   Mon, 7 Dec 2020 20:45:15 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Greg KH <greg@...ah.com>
Cc:     Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
        "H. Peter Anvin" <hpa@...or.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Jonathan Cameron <Jonathan.Cameron@...wei.com>,
        Lars-Peter Clausen <lars@...afoo.de>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the staging tree

Hi Greg,

On Mon, 7 Dec 2020 10:26:06 +0100 Greg KH <greg@...ah.com> wrote:
>
> > diff --git a/drivers/iio/trigger/iio-trig-sysfs.c b/drivers/iio/trigger/iio-trig-sysfs.c
> > index 10a3fd29362b..0f6b512a5c37 100644
> > --- a/drivers/iio/trigger/iio-trig-sysfs.c
> > +++ b/drivers/iio/trigger/iio-trig-sysfs.c
> > @@ -160,8 +160,7 @@ static int iio_sysfs_trigger_probe(int id)
> >  	t->trig->dev.parent = &iio_sysfs_trig_dev;
> >  	iio_trigger_set_drvdata(t->trig, t);
> >  
> > -	init_irq_work(&t->work, iio_sysfs_trigger_work);
> > -	atomic_set(&t->work.flags, IRQ_WORK_HARD_IRQ);
> > +	t->work = IRQ_WORK_INIT_HARD(iio_sysfs_trigger_work);
> >  
> >  	ret = iio_trigger_register(t->trig);
> >  	if (ret)
> > -- 
> > 2.29.2  
> 
> Is this patch "safe" to take now, if the tip tree isn't part of my tree?

Unfortunately not, as IRQ_WORK_INIT_HARD() is introduced by the tip tree
commit.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped