From: Andrew Morton <akpm@osdl.org>
To: "Komal Shah" <komal_shah802003@yahoo.com>
Cc: linux-input@atrey.karlin.mff.cuni.cz, dtor_core@ameritech.net,
tony@atomide.com, ext-timo.teras@nokia.com,
juha.yrjola@solidboot.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] OMAP: Keypad driver
Date: Sat, 22 Jul 2006 02:39:35 -0700 [thread overview]
Message-ID: <20060722023935.aab52bd2.akpm@osdl.org> (raw)
In-Reply-To: <1153556774.4920.266617704@webmail.messagingengine.com>
On Sat, 22 Jul 2006 01:26:14 -0700
"Komal Shah" <komal_shah802003@yahoo.com> wrote:
> Please review the attached TI OMAP Keypad driver patch
> and consider it for -mm submission.
The code looks clean.
- Could use setup_timer().
- Check the return value from device_create_file() (and any and all such
similar functions), handle failure appropriately.
- I don't think the tasklet stopping code is correct. tasklet_disable()
will prevent the callback from being called. The del_timer_sync() will
kill off the timer. But the just-killed timer handler might have left
the tasklet scheduled, and although it will not call the handler, the
high-level tasklet code can still execute, and will then start playing
with now-freed data. A final tasklet_kill() should fix that up.
- Perhaps the probe function is requesting the IRQ too early? The IRQ
handler can perhaps be called while the hardware is still being set up.
- Use INTF_TRIGGER_FALLING (etc), not the now-deprecated SA_TRIGGER_FALLING.
- The changelog needs work. What's an OMAP? ;)
- Finally, by what authority does random_person@yahoo.com submit Nokia
and TI's code?? Please review Section 11 of
Documentation/SubmittingPatches, seek and obtain signoffs from the other
authors and then add your own, thanks.
next prev parent reply other threads:[~2006-07-22 9:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-22 8:26 [PATCH] OMAP: Keypad driver Komal Shah
2006-07-22 9:39 ` Andrew Morton [this message]
2006-07-22 10:13 ` Komal Shah
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=20060722023935.aab52bd2.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=dtor_core@ameritech.net \
--cc=ext-timo.teras@nokia.com \
--cc=juha.yrjola@solidboot.com \
--cc=komal_shah802003@yahoo.com \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.