From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: "Zephaniah E. Hull" <warp@aehallh.com>
Cc: "Komal Shah" <komal_shah802003@yahoo.com>,
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 08:26:46 -0400 [thread overview]
Message-ID: <d120d5000608290526i208885f4u9eed3269e1d3ffb1@mail.gmail.com> (raw)
In-Reply-To: <20060829104049.GB4181@aehallh.com>
On 8/29/06, Zephaniah E. Hull <warp@aehallh.com> wrote:
> On Tue, Aug 29, 2006 at 01:55:37AM -0700, Komal Shah wrote:
> > --- "Zephaniah E. Hull" <warp@aehallh.com> wrote:
> > >
> > > -psmouse-objs := psmouse-base.o alps.o logips2pp.o synaptics.o
> > > lifebook.o trackpoint.o
> > > +psmouse-objs := psmouse-base.o alps.o logips2pp.o synaptics.o
> > > lifebook.o trackpoint.o olpc.o
> >
> > Where is KConfigurable entry ?
>
> It is a component of psmouse.o, which is a few lines up.
>
> Breaking out the components of psmouse.o into separate configuration
> items might be interesting, but it is quite a bit beyond the scope of
> this patch.
Is there a chance that this device will be used on generally-available
hardware? If not then having Kconfig sub-option would be nice.
> >
> > > diff --git a/drivers/input/mouse/olpc.c b/drivers/input/mouse/olpc.c
> > > new file mode 100644
> > > index 0000000..245f29e
> > > --- /dev/null
> > > +++ b/drivers/input/mouse/olpc.c
> > > @@ -0,0 +1,327 @@
> >
> >
> > > +/*
> > > + * OLPC touchpad PS/2 mouse driver
> > > + *
> > > +int olpc_init(struct psmouse *psmouse)
> > > +{
> > > + struct olpc_data *priv;
> > > + struct input_dev *dev = psmouse->dev;
> > > + struct input_dev *dev2;
> > > +
> > > + psmouse->private = priv = kzalloc(sizeof(struct olpc_data),
> > > GFP_KERNEL);
> >
> > I think you should assign priv to private only if !NULL.
>
> Fixed.
>
> It should not actually matter, as a failure to get a !NULL value causes
> us to return false, which will fall over to other psmouse drivers which
> will either set it themselves, or not use it at all, however.
>
> It should be noted that alps.c contains the same issue.
>
I do not consider this is an issue. priv is just a shortcut or alias
for psmouse->private that saves some typing and allows the compiled to
generate better code.
--
Dmitry
next prev parent reply other threads:[~2006-08-29 12:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-29 7:33 Zephaniah E. Hull
2006-08-29 8:10 ` Arjan van de Ven
2006-08-29 8:44 ` Zephaniah E. Hull
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 [this message]
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=d120d5000608290526i208885f4u9eed3269e1d3ffb1@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=komal_shah802003@yahoo.com \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=warp@aehallh.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
all inboxes | Powered by JetHome®