From: "Zephaniah E. Hull" <warp@aehallh.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-input@atrey.karlin.mff.cuni.cz,
linux-kernel@vger.kernel.org,
Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [RPC] OLPC tablet input driver.
Date: Tue, 29 Aug 2006 04:44:43 -0400 [thread overview]
Message-ID: <20060829084443.GA4187@aehallh.com> (raw)
In-Reply-To: <1156839019.2722.39.camel@laptopd505.fenrus.org>
[-- Attachment #1: Type: text/plain, Size: 2381 bytes --]
On Tue, Aug 29, 2006 at 10:10:19AM +0200, Arjan van de Ven wrote:
> > +#undef DEBUG
> > +#ifdef DEBUG
> > +#define dbg(format, arg...) printk(KERN_INFO "olpc.c(%d): " format "\n", __LINE__, ## arg)
> > +#else
> > +#define dbg(format, arg...) do {} while (0)
> > +#endif
>
> why not use pr_debug or even dev_debug() ?
> Those already have this ifdef included
I was not thinking of them at the time, however dev_dbg is not an option
because we do not have a struct device at hand when we want to print
some debugging lines.
pr_debug might work, but I would rather have file and line already
there.
Though, admittedly, that would be a better argument if it used __FILE__
there instead of hard coding it.
In any case, I don't think any of the debug prints will have to stick
around that much longer.
>
> > +
> > +static struct olpc_model_info olpc_model_data[] = {
> > + { { 0x67, 0x00, 0x0a }, 0xeb, 0xff, OLPC_PTGS }, /* OLPC in PT+GS mode. */
> > +};
>
> const?
Added.
(Along with associated changes so that it's kept const everywhere.)
>
> also.. there's no locking visible anywhere in the driver... is this
> right?
It looks like psmouse handles it with a mutex lock around freeing stuff
and calling the callback function pointers we set on init, so we
_should_ be safe unless I've missed something.
Add to it that none of the other psmouse drivers are doing locking on
their own, and I'm fairly sure that this is correct. (But if someone
knows better, please correct me.)
Thank you.
Zephaniah E. Hull.
--
1024D/E65A7801 Zephaniah E. Hull <warp@aehallh.com>
92ED 94E4 B1E6 3624 226D 5727 4453 008B E65A 7801
CCs of replies from mailing lists are requested.
Mike Sphar (Scary Devil Monastery):
>I am hired because I know what I am doing, not because I will do
>whatever I am told is a good idea. This might cost me bonuses, raises,
>promotions, and may even label me as "undesirable" by places I don't
>want to work at anyway, but I don't care. I will not compromise my own
>principles and judgement without putting up a fight. Of course, I
>won't always win, and I will sometimes be forced to do things I don't
>agree with, but if I am my objections will be known, and if I am shown
>to be right and problems later develop, I will shout "I told you so!"
>repeatedly, laugh hysterically, and do a small dance or jig as
>appropriate to my heritage.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-08-29 8:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-29 7:33 [RPC] OLPC tablet input driver Zephaniah E. Hull
2006-08-29 8:10 ` Arjan van de Ven
2006-08-29 8:44 ` Zephaniah E. Hull [this message]
2006-08-29 12:29 ` Dmitry Torokhov
2006-08-30 4:45 ` Greg KH
2006-08-29 8:55 ` Komal Shah
2006-08-29 10:40 ` Zephaniah E. Hull
2006-08-29 12:26 ` Dmitry Torokhov
2006-08-29 9:00 ` Komal Shah
2006-08-29 12:53 ` Dmitry Torokhov
2006-08-29 14:35 ` Zephaniah E. Hull
2006-08-29 15:12 ` Dmitry Torokhov
2006-09-10 20:10 ` [RFC] OLPC tablet input driver, take two Zephaniah E. Hull
2006-09-10 22:19 ` Dmitry Torokhov
2006-09-11 18:27 ` Zephaniah E. Hull
2006-09-11 19:01 ` Dmitry Torokhov
2006-09-11 19:03 ` Zephaniah E. Hull
2006-09-11 19:02 ` [RFC] OLPC tablet input driver, take three Zephaniah E. Hull
2006-09-11 19:10 ` Dmitry Torokhov
2006-09-12 19:39 ` Zephaniah E. Hull
2006-09-12 19:58 ` Dmitry Torokhov
2006-11-08 12:04 ` [RPC] OLPC tablet input driver Vojtech Pavlik
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=20060829084443.GA4187@aehallh.com \
--to=warp@aehallh.com \
--cc=arjan@infradead.org \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
/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