All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ftp.linux.org.uk>
To: Pavel Machek <pavel@ucw.cz>
Cc: rpurdie@rpsys.net, lenz@cs.wisc.edu,
	kernel list <linux-kernel@vger.kernel.org>,
	Russell King <rmk@arm.linux.org.uk>,
	Dirk@Opfer-Online.de, arminlitzel@web.de, pavel.urban@ct.cz,
	metan@seznam.cz
Subject: Re: Nasty warnings on arm (+ one compile problem -- INIT_WORK related)
Date: Sat, 16 Dec 2006 01:09:06 +0000	[thread overview]
Message-ID: <20061216010906.GC17561@ftp.linux.org.uk> (raw)
In-Reply-To: <20061215235818.GD2853@elf.ucw.cz>

 
> Plus compile error. It should be some search&replace I should do, but
> which one?
> 
> drivers/video/sa1100fb.c:1447:49: macro "INIT_WORK" passed 3
> arguments, but takes just 2
> drivers/video/sa1100fb.c: In function `sa1100fb_init_fbinfo':
> drivers/video/sa1100fb.c:1447: error: `INIT_WORK' undeclared (first
> use in this function)
> drivers/video/sa1100fb.c:1447: error: (Each undeclared identifier is
> reported only once
> drivers/video/sa1100fb.c:1447: error: for each function it appears
> in.)
> drivers/video/sa1100fb.c: At top level:
> drivers/video/sa1100fb.c:1204: warning: `sa1100fb_task' defined but
> not used
> make[2]: *** [drivers/video/sa1100fb.o] Error 1
> make[1]: *** [drivers/video] Error 2
> make: *** [drivers] Error 2
> 
>         INIT_WORK(&fbi->task, sa1100fb_task, fbi);
> 
> ...
> 
> /*
>  * Our LCD controller task (which is called when we blank or unblank)
>  * via keventd.
>  */
> static void sa1100fb_task(void *dummy)
> {
>         struct sa1100fb_info *fbi = dummy;
>         u_int state = xchg(&fbi->task_state, -1);
> 
>         set_ctrlr_state(fbi, state);
> }
> 
> (Or will I need to play with container_of or something? I guess I did
> not pay attetion to workqueue stuff).

... and that's

static void sa1100fb_task(struct work_struct *ucking_fugly)
{
	struct sa1100fb_info *fbi = container_of(ucking_fugly,
						 struct sa1100fb_info,
						 task);

  parent reply	other threads:[~2006-12-16  1:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-15 23:58 Nasty warnings on arm (+ one compile problem -- INIT_WORK related) Pavel Machek
2006-12-16  1:07 ` Al Viro
2006-12-16  1:09 ` Al Viro [this message]
2006-12-17 12:33   ` Pavel Machek
2006-12-16 12:10 ` Russell King

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061216010906.GC17561@ftp.linux.org.uk \
    --to=viro@ftp.linux.org.uk \
    --cc=Dirk@Opfer-Online.de \
    --cc=arminlitzel@web.de \
    --cc=lenz@cs.wisc.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=metan@seznam.cz \
    --cc=pavel.urban@ct.cz \
    --cc=pavel@ucw.cz \
    --cc=rmk@arm.linux.org.uk \
    --cc=rpurdie@rpsys.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.