Hi!
> >> > 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
> "Pavel" == Pavel Machek <[EMAIL PROTECTED]> 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
Pavel == Pavel Machek [EMAIL PROTECTED] 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
Hi!
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
Hi!
> > Pavel> Hi! Two Long time ago, BenH said that making patches is easy,
> > Pavel> so I hope to get his help now... And will probably need more.
> >
> > Pavel> Suspend routines change, slowly.
> >
> > Pavel> - int (*suspend)(struct device * dev, u32 state); + int
> > Pavel>
Hi!
Pavel Hi! Two Long time ago, BenH said that making patches is easy,
Pavel so I hope to get his help now... And will probably need more.
Pavel Suspend routines change, slowly.
Pavel - int (*suspend)(struct device * dev, u32 state); + int
Pavel (*suspend)(struct device * dev,
6 matches
Mail list logo
