Re: Problem with request_irq

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Monday 11 June 2007 15:10, Christian Stalp wrote:
> Hello again,
> I have another problem with my driver. This time it is the
> request_irq-call.
>
> I got this code, where there is a linked list:
> LIST_HEAD(me1400_info_list);
>
> then later this list is used to fill my structs inside the open-function:
>
> struct list_head *ptr;
> me1400_info_type *info = NULL;
>
> for(ptr = me1400_info_list.next, i = 0; ptr != &me1400_info_list; ptr =
> ptr->next, i++) {
> 	info = list_entry(ptr, me1400_info_type, list);
> 	if(i == minor) break;
> }
>
> with that this struct is used (casted to void) to initiade the
> request_irq-call:
>
> err = request_irq(info->int_line,
> 				me1400_isr,
> 				SA_INTERRUPT | SA_SHIRQ,
> 				ME1400_NAME,
> 				(void *) info);
>
> The problem now is, that I get this warning:
> /home/chris/tmp/me1400-1.2.12/me1400.c: In function ‘me1400_open’:
> /home/chris/tmp/me1400-1.2.12/me1400.c:672: warning: passing argument 2 of
> ‘request_irq’ from incompatible pointer type
>

Most likely, the prototype of me1400_isr is wrong.

tavi

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ



[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux