From: "Mohammad A. Haque" <mhaque@haque.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Miles Lane <miles@megapathdsl.net>,
Frank Davis <fdavis112@juno.com>,
linux-kernel@vger.kernel.org
Subject: Re: INIT_LIST_HEAD marco audit
Date: Mon, 11 Dec 2000 08:19:17 -0500 [thread overview]
Message-ID: <3A34D455.7208BE2F@haque.net> (raw)
In-Reply-To: <E145SRT-0007sM-00@the-village.bc.nu>
Thinko.
Question is... Adam Richter posted a patch for i2o_lan.c that does
this...
static struct tq_struct i2o_post_buckets_task = {
list: LIST_HEAD_INIT(i2o_post_buckets_task.list),
sync: 0,
routine: (void (*)(void *))i2o_lan_receive_post,
data: (void *) 0
};
If that's correct then is the only fix for structures similar to
tcic_task to type cast the routine?
Alan Cox wrote:
>
> > -static struct tq_struct tcic_task = {
> > - routine: tcic_bh
> > +DECLARE_TASK_QUEUE(tcic_task);
> > +struct tq_struct run_tcic_task = {
> > + routine: (void (*)(void *)) tcic_bh
> > };
>
> Why remove the 'static' ?
--
=====================================================================
Mohammad A. Haque http://www.haque.net/
mhaque@haque.net
"Alcohol and calculus don't mix. Project Lead
Don't drink and derive." --Unknown http://wm.themes.org/
batmanppc@themes.org
=====================================================================
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-11 13:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-11 0:42 INIT_LIST_HEAD marco audit Frank Davis
2000-12-11 0:46 ` Mohammad A. Haque
2000-12-11 2:54 ` Mohammad A. Haque
2000-12-11 3:22 ` Mohammad A. Haque
2000-12-11 3:50 ` Miles Lane
2000-12-11 4:14 ` Mohammad A. Haque
2000-12-11 12:52 ` Alan Cox
2000-12-11 13:19 ` Mohammad A. Haque [this message]
2000-12-11 23:07 ` Andrew Morton
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=3A34D455.7208BE2F@haque.net \
--to=mhaque@haque.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=fdavis112@juno.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miles@megapathdsl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox