linux-kernel - Re: [PATCH] staging: Complete sched.h removal from interrupt.h

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:	Tue, 13 Oct 2009 10:24:11 -0400
From:	Jeff Mahoney <jeffm@...e.com>
To:	Jonathan Cameron <Jonathan.Cameron@...il.com>
Cc:	Greg KH <gregkh@...e.de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] staging: Complete sched.h removal from interrupt.h

On 10/13/2009 07:08 AM, Jonathan Cameron wrote:
> Hi Jeff,
>>  drivers/staging/iio/industrialio-core.c    |    2 ++
>>   
> ...
>> --- a/drivers/staging/iio/industrialio-core.c
>> +++ b/drivers/staging/iio/industrialio-core.c
>> @@ -19,6 +19,8 @@
>>  #include <linux/interrupt.h>
>>  #include <linux/poll.h>
>>  #include <linux/cdev.h>
>> +#include <linux/sched.h>
>> +#include <linux/wait.h>
>>  #include "iio.h"
>>  #include "trigger_consumer.h"
>>   
> Greg has already picked up a patch for this one, but might make more
> sense to drop
> that and merge all these fixes as one.  Original patch only added
> sched.h though.
> Is wait.h due to a similar issue that is going to bite in the future?
> (could chase this
> down but as you added it seemed easier to ask!)

Nope, I think iio was probably the first driver I saw this build failure
in and observed that it was in the wait queue code. It's not necessary,
though it doesn't cost anything either since wait.h is already included
somewhere.

-Jeff

-- 
Jeff Mahoney
SUSE Labs
--
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/