From: Randy Dunlap <randy.dunlap@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Eric Piel <eric.piel@tremplin-utc.net>,
linux-kernel@vger.kernel.org, pavel@suse.cz,
burman.yan@gmail.com, pau@eslack.org
Subject: Re: [PATCH] LIS3LV02Dx Accelerometer driver (take 4)
Date: Tue, 21 Oct 2008 11:53:25 -0700 [thread overview]
Message-ID: <48FE2525.90701@oracle.com> (raw)
In-Reply-To: <20081021114121.5144841c.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Sat, 18 Oct 2008 21:05:12 +0200
> Eric Piel <eric.piel@tremplin-utc.net> wrote:
>
>> ...
>>
>> +/**
>> + * lis3lv02d_acpi_read() - ACPI ALRD method: read a register
>
> All the kerneldoc comments include the () after the function name.
> That is unconventional and I do not know what effect it will have upon
> kerneldoc processing and output.
Yes, it's unconventional.
It works. It (the "()") will be dropped when processed.
>> + * @handle: the handle of the device
>> + * @reg: the register to read
>> + * @ret: result of the operation
>> + *
>> + * Returns AE_OK on success.
>> + */
>> +static acpi_status lis3lv02d_acpi_read(acpi_handle handle, int reg, u8 *ret)
>> +{
next prev parent reply other threads:[~2008-10-21 18:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-18 19:05 [PATCH] LIS3LV02Dx Accelerometer driver (take 4) Eric Piel
2008-10-19 16:34 ` Jonathan Cameron
2008-10-19 23:07 ` Eric Piel
2008-10-20 13:32 ` Jonathan Cameron
2008-10-21 8:38 ` Pavel Machek
2008-10-21 18:42 ` Andrew Morton
2008-10-22 10:27 ` Pavel Machek
2008-10-22 11:34 ` Eric Piel
2008-10-22 11:58 ` Pavel Machek
2008-10-21 18:41 ` Andrew Morton
2008-10-21 18:53 ` Randy Dunlap [this message]
2008-10-21 20:48 ` Eric Piel
2008-10-21 22:13 ` Eric Piel
2008-10-21 22:21 ` Andrew Morton
2008-10-22 15:20 ` Pavel Machek
2008-10-22 18:51 ` Len Brown
2008-10-23 8:11 ` Eric Piel
2008-10-23 8:24 ` Pavel Machek
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=48FE2525.90701@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=burman.yan@gmail.com \
--cc=eric.piel@tremplin-utc.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pau@eslack.org \
--cc=pavel@suse.cz \
/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