From: Greg KH <greg@kroah.com>
To: Rodolfo Giometti <giometti@enneenne.com>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: Oops: [RFC] LinuxPPS (pre)patch
Date: Sat, 20 Oct 2007 21:06:41 -0700 [thread overview]
Message-ID: <20071021040641.GB24869@kroah.com> (raw)
In-Reply-To: <20071019175323.GA20453@enneenne.com>
On Fri, Oct 19, 2007 at 07:53:24PM +0200, Rodolfo Giometti wrote:
> +/* The main struct */
> +struct pps_device {
> + struct pps_source_info info; /* PSS source info */
> +
> + struct pps_kparams params; /* PPS's current params */
> +
> + __u32 assert_sequence; /* PPS' assert event seq # */
> + __u32 clear_sequence; /* PPS' clear event seq # */
> + struct pps_ktime assert_tu;
> + struct pps_ktime clear_tu;
> + int current_mode; /* PPS mode at event time */
> +
> + int go; /* PPS event is arrived? */
> + wait_queue_head_t queue; /* PPS event queue */
> +
> + unsigned int id; /* PPS source unique ID */
> + struct cdev cdev;
> + struct device *dev;
> + int devno;
> + struct fasync_struct *async_queue; /* fasync method */
> + spinlock_t lock;
> +
> + atomic_t usage; /* usage count */
> + wait_queue_head_t usage_queue;
> +
> + struct class_device class_dev;
> +};
Please use a 'struct class' instead of a 'struct class_device'. We have
almost rid the kernel of all usages of 'struct class_device' and want to
remove that structure entirely soon. I'm aiming for 2.6.25 and it's
looking good.
So please don't add new instances of it, you can do all the same things
with a 'struct device' and it should be a very trivial change.
thanks,
greg k-h
next prev parent reply other threads:[~2007-10-21 4:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 17:41 [RFC] LinuxPPS (pre)patch Rodolfo Giometti
2007-10-19 17:53 ` Oops: " Rodolfo Giometti
2007-10-21 4:06 ` Greg KH [this message]
2007-10-22 19:47 ` Rodolfo Giometti
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=20071021040641.GB24869@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=dwmw2@infradead.org \
--cc=giometti@enneenne.com \
--cc=linux-kernel@vger.kernel.org \
/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