From: Jes Sorensen <jes@wildopensource.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-pm@osdl.org, kernel-janitors@osdl.org,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [linux-pm] Re: driver model u32 -> pm_message_t conversion: help needed
Date: 03 Feb 2005 04:09:30 -0500 [thread overview]
Message-ID: <yq0y8e6ovqt.fsf@jaguar.mkp.net> (raw)
In-Reply-To: <20050202095739.GB12955@elf.ucw.cz>
>>>>> "Pavel" == Pavel Machek <pavel@ucw.cz> writes:
>> > Sorry for being late responding to this, but I'd say this is a
>> prime > example for typedef's considered evil (see Greg's OLS talk
>> ;).
>> >
>> > It would be a lot cleaner if it was made a struct and then
>> passing a > struct pointer as the argument instead of passing the
>> struct by value > as you do right now.
>>
>> Sorry, can't do that. That would require flag day and change
>> everything at once. That is just not feasible. When things are
>> settled, it is okay to change it to struct passed by value.. It is
>> small anyway and at least we will not have problems with freeing it
>> etc.
Pavel> Well, we could switch to passing struct by reference
Pavel> (typedef struct pm_message *pm_message_t)
Pavel> , but AFAICS it would only bring us problems with lifetime
Pavel> rules etc. Lets not do it. Pavel
This way you end up hiding what is really going on, the very problem
of using typedefs. If the change is really needed why not get it right
in the first go?
Cheers,
Jes
next prev parent reply other threads:[~2005-02-03 9:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-25 19:47 Pavel Machek
2005-01-25 23:50 ` Benjamin Herrenschmidt
2005-02-02 0:09 ` Daniel Drake
2005-02-02 0:10 ` Pavel Machek
2005-02-02 8:30 ` Jes Sorensen
2005-02-02 9:50 ` Pavel Machek
2005-02-02 9:57 ` [linux-pm] " Pavel Machek
2005-02-03 9:09 ` Jes Sorensen [this message]
2005-02-03 10:38 ` Pavel Machek
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=yq0y8e6ovqt.fsf@jaguar.mkp.net \
--to=jes@wildopensource.com \
--cc=kernel-janitors@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@osdl.org \
--cc=pavel@ucw.cz \
/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
all inboxes | Powered by JetHome®