From: "Kevin O'Connor" <kevin@koconnor.net>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] Workqueue Abstraction, 2.5.40-H7
Date: Wed, 2 Oct 2002 21:38:59 -0400 [thread overview]
Message-ID: <20021002213859.A27014@arizona.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44.0210012219460.21087-100000@localhost.localdomain>; from mingo@elte.hu on Tue, Oct 01, 2002 at 10:29:02PM +0200
On Tue, Oct 01, 2002 at 10:29:02PM +0200, Ingo Molnar wrote:
> On Tue, 1 Oct 2002, Linus Torvalds wrote:
> > Pease don't introduce more typedefs. They only hide what the hell the
> > thing is, which is actively _bad_ for structures, since passing a
[...]
> Despite all the previous fuss about the problems of typedefs, i've never
> had *any* problem with using typedefs in various code i wrote. It only
> ever made things cleaner - to me.
Hi Ingo,
I follow your reasoning, but one thing I don't follow -
+typedef struct work_s {
+ unsigned long pending;
+ struct list_head entry;
+ void (*func)(void *);
+ void *data;
+ void *wq_data;
+ timer_t timer;
+} work_t;
- why two names for the structure ("struct work_s" and "work_t")?
Either convention will work, but by declaring the structure twice it only
encourages users to employ their own favorite - thus defeating the purpose
of a convention.
Just curious,
-Kevin
--
------------------------------------------------------------------------
| Kevin O'Connor "BTW, IMHO we need a FAQ for |
| kevin@koconnor.net 'IMHO', 'FAQ', 'BTW', etc. !" |
------------------------------------------------------------------------
next prev parent reply other threads:[~2002-10-03 1:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 20:29 [patch] Workqueue Abstraction, 2.5.40-H7 Ingo Molnar
2002-10-01 20:49 ` Linus Torvalds
2002-10-01 21:21 ` Ingo Molnar
2002-10-02 3:23 ` Miles Bader
2002-10-02 19:18 ` Randy.Dunlap
2002-10-01 21:09 ` Jes Sorensen
2002-10-01 21:35 ` Ingo Molnar
2002-10-03 1:38 ` Kevin O'Connor [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-01 18:52 Marc-Christian Petersen
2002-10-02 3:58 ` Christoph Hellwig
2002-10-01 16:24 Ingo Molnar
2002-10-01 17:55 ` Kai Germaschewski
2002-10-01 21:27 ` Ingo Molnar
2002-10-01 18:04 ` Jeff Garzik
2002-10-01 18:52 ` Ingo Molnar
2002-10-01 21:06 ` Jeff Garzik
2002-10-01 21:30 ` Ingo Molnar
2002-10-01 19:16 ` Linus Torvalds
2002-10-01 19:53 ` Linus Torvalds
2002-10-01 21:32 ` Kristian Hogsberg
2002-10-03 18:44 ` Ingo Molnar
2002-10-04 23:20 ` Kristian Hogsberg
2002-10-02 4:22 ` Christoph Hellwig
2002-10-01 21:31 ` Ingo Molnar
2002-10-02 8:22 ` Oleg Drokin
2002-10-08 3:50 ` Jeff Dike
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=20021002213859.A27014@arizona.localdomain \
--to=kevin@koconnor.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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;
as well as URLs for NNTP newsgroup(s).