From: Frans Pop <elendil@planet.nl>
To: pavel@suse.cz
Cc: "Éric Piel" <eric.piel@tremplin-utc.net>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
trenn@suse.de
Subject: Re: hp accelerometer: add freefall detection
Date: Sat, 14 Feb 2009 17:01:01 +0100 [thread overview]
Message-ID: <200902141701.02876.elendil@planet.nl> (raw)
In-Reply-To: <4992C57E.9050109@tremplin-utc.net>
Hi Pavel,
> +++ b/drivers/hwmon/lis3lv02d.c
[...]
> +static int lis3lv02d_misc_open(struct inode *inode, struct file *file)
[...]
> + if (ret) {
> + clear_bit(0, &adev.misc_opened);
> + printk(KERN_ERR DRIVER_NAME ": IRQ%d allocation failed\n", ad
> + return -EBUSY;
> + }
> + lis3lv02d_increase_use(&adev);
> + printk("lis3: registered interrupt %d\n", adev.irq);
Is this a debug printk that should be removed altogether or should it
be given a proper format and KERN_DEBUG?
> + return 0;
> +}
[...]
> @@ -268,6 +393,19 @@ int lis3lv02d_init_device(struct acpi_lis3lv02d
> *dev) if (lis3lv02d_joystick_enable())
> printk(KERN_ERR DRIVER_NAME ": joystick initialization failed
>
> + printk("lis3_init_device: irq %d\n", dev->irq);
Same here.
> +
> + /* if we did not get an IRQ from ACPI - we have nothing more to do */
> + if (!dev->irq) {
> + printk(KERN_ERR DRIVER_NAME
> + ": No IRQ in ACPI. Disabling /dev/freefall\n");
> + goto out;
> + }
> +
> + printk("lis3: registering device\n");
And here.
> + if (misc_register(&lis3lv02d_misc_device))
> + printk(KERN_ERR DRIVER_NAME ": misc_register failed\n");
Cheers,
FJP
next prev parent reply other threads:[~2009-02-14 16:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200901162234.n0GMYB8Z022317@imap1.linux-foundation.org>
2009-02-11 12:33 ` hp accelerometer: add freefall detection Éric Piel
2009-02-13 12:28 ` Pavel Machek
2009-02-14 16:01 ` Frans Pop [this message]
2009-03-08 21:14 ` Pavel Machek
2009-01-12 9:29 hp accelerometer: fix LED handling and " Pavel Machek
2009-01-12 9:33 ` Éric Piel
2009-01-16 12:19 ` hp accelerometer: " Pavel Machek
2009-01-16 22:34 ` Andrew Morton
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=200902141701.02876.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=akpm@linux-foundation.org \
--cc=eric.piel@tremplin-utc.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=trenn@suse.de \
/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