From: gbittencourt <gabrielabittencourt00@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>,
outreachy-kernel@googlegroups.com, sudipm.mukherjee@gmail.com,
teddy.wang@siliconmotion.com, gregkh@linuxfoundation.org,
linux-fbdev@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, lkcamp@lists.libreplanetbr.org,
trivial@kernel.org
Subject: Re: [PATCH] staging: sm750fb: format description of parameters the to kernel doc format
Date: Wed, 16 Oct 2019 22:29:27 -0300 [thread overview]
Message-ID: <d55516db-28c5-aa53-8d07-20201dc4ffca@gmail.com> (raw)
In-Reply-To: <799632e2-a328-d72b-397d-3ee6b5e87e06@infradead.org>
Hi Randy,
On 10/16/19 10:25 PM, Randy Dunlap wrote:
> Hi,
>
> On 10/16/19 6:18 PM, Gabriela Bittencourt wrote:
>> Cluster comments that describes parameters of functions and create one
>> single comment before the function in kernel doc format.
> Good plan.
>
> How did you test this patch?
I haven't test it. How can I do it?
>
>> Signed-off-by: Gabriela Bittencourt <gabrielabittencourt00@gmail.com>
>> ---
>> drivers/staging/sm750fb/sm750_accel.c | 65 +++++++++++++++------------
>> 1 file changed, 37 insertions(+), 28 deletions(-)
>>
>> diff --git a/drivers/staging/sm750fb/sm750_accel.c b/drivers/staging/sm750fb/sm750_accel.c
>> index dbcbbd1055da..d5564cd60f3b 100644
>> --- a/drivers/staging/sm750fb/sm750_accel.c
>> +++ b/drivers/staging/sm750fb/sm750_accel.c
>> @@ -130,20 +130,24 @@ int sm750_hw_fillrect(struct lynx_accel *accel,
>> return 0;
>> }
>>
>> -int sm750_hw_copyarea(
>> -struct lynx_accel *accel,
>> -unsigned int sBase, /* Address of source: offset in frame buffer */
>> -unsigned int sPitch, /* Pitch value of source surface in BYTE */
>> -unsigned int sx,
>> -unsigned int sy, /* Starting coordinate of source surface */
>> -unsigned int dBase, /* Address of destination: offset in frame buffer */
>> -unsigned int dPitch, /* Pitch value of destination surface in BYTE */
>> -unsigned int Bpp, /* Color depth of destination surface */
>> -unsigned int dx,
>> -unsigned int dy, /* Starting coordinate of destination surface */
>> -unsigned int width,
>> -unsigned int height, /* width and height of rectangle in pixel value */
>> -unsigned int rop2) /* ROP value */
>> +/**
> Missing function name and short description. Documentation/doc-guide/kernel-doc.rst says:
>
> The general format of a function and function-like macro kernel-doc comment is::
>
> /**
> * function_name() - Brief description of function.
> * @arg1: Describe the first argument.
> * @arg2: Describe the second argument.
> * One can provide multiple line descriptions
> * for arguments.
> *
> * A longer description, with more discussion of the function function_name()
> * that might be useful to those using or modifying it. Begins with an
> * empty comment line, and may include additional embedded empty
> * comment lines.
> *
> * The longer description may have multiple paragraphs.
> *
> * Context: Describes whether the function can sleep, what locks it takes,
> * releases, or expects to be held. It can extend over multiple
> * lines.
> * Return: Describe the return value of function_name.
> *
> * The return value description can also have multiple paragraphs, and should
> * be placed at the end of the comment block.
> */
>
>> + * @sBase: Address of source: offset in frame buffer
>> + * @sPitch: Pitch value of source surface in BYTE
>> + * @sx, @sy: Starting coordinate of source surface
> Those should be on separate lines.
>
>> + * @dBase: Address of destination: offset in frame buffer
>> + * @dPitch: Pitch value of destination surface in BYTE
>> + * @Bpp: Color depth of destination surface
>> + * @dx, @dy: Starting coordinate of destination surface
> Ditto.
>
>> + * @width, @height: width and height of rectangle in pixel value
>> + * @rop2: ROP value
>> + */
>> +int sm750_hw_copyarea(struct lynx_accel *accel,
>> + unsigned int sBase, unsigned int sPitch,
>> + unsigned int sx, unsigned int sy,
>> + unsigned int dBase, unsigned int dPitch,
>> + unsigned int Bpp, unsigned int dx, unsigned int dy,
>> + unsigned int width, unsigned int height,
>> + unsigned int rop2)
>> {
>> unsigned int nDirection, de_ctrl;
>>
>> @@ -288,20 +292,25 @@ static unsigned int deGetTransparency(struct lynx_accel *accel)
>> return de_ctrl;
>> }
>>
>> -int sm750_hw_imageblit(struct lynx_accel *accel,
>> - const char *pSrcbuf, /* pointer to start of source buffer in system memory */
>> - u32 srcDelta, /* Pitch value (in bytes) of the source buffer, +ive means top down and -ive mean button up */
>> - u32 startBit, /* Mono data can start at any bit in a byte, this value should be 0 to 7 */
>> - u32 dBase, /* Address of destination: offset in frame buffer */
>> - u32 dPitch, /* Pitch value of destination surface in BYTE */
>> - u32 bytePerPixel, /* Color depth of destination surface */
>> - u32 dx,
>> - u32 dy, /* Starting coordinate of destination surface */
>> - u32 width,
>> - u32 height, /* width and height of rectangle in pixel value */
>> - u32 fColor, /* Foreground color (corresponding to a 1 in the monochrome data */
>> - u32 bColor, /* Background color (corresponding to a 0 in the monochrome data */
>> - u32 rop2) /* ROP value */
>> +/**
> Similar comments here...
>
>> + * @pSrcbuf: pointer to start of source buffer in system memory
>> + * @srcDelta: Pitch value (in bytes) of the source buffer, +ive means top down
>> + * and -ive mean button up
>> + * @startBit: Mono data can start at any bit in a byte, this value should be
>> + * 0 to 7
>> + * @dBase: Address of destination: offset in frame buffer
>> + * @dPitch: Pitch value of destination surface in BYTE
>> + * @bytePerPixel: Color depth of destination surface
>> + * @dx, @dy: Starting coordinate of destination surface
>> + * @width, @height: width and height of rectangle in pixel value
>> + * @fColor: Foreground color (corresponding to a 1 in the monochrome data
>> + * @bColor: Background color (corresponding to a 0 in the monochrome data
>> + * @rop2: ROP value
>> + */
>> +int sm750_hw_imageblit(struct lynx_accel *accel, const char *pSrcbuf,
>> + u32 srcDelta, u32 startBit, u32 dBase, u32 dPitch,
>> + u32 bytePerPixel, u32 dx, u32 dy, u32 width,
>> + u32 height, u32 fColor, u32 bColor, u32 rop2)
>> {
>> unsigned int ulBytesPerScan;
>> unsigned int ul4BytesPerScan;
>>
> Thanks.
Thanks.
next prev parent reply other threads:[~2019-10-17 1:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 1:18 Gabriela Bittencourt
2019-10-17 1:25 ` Randy Dunlap
2019-10-17 1:29 ` gbittencourt [this message]
2019-10-17 1:52 ` Randy Dunlap
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=d55516db-28c5-aa53-8d07-20201dc4ffca@gmail.com \
--to=gabrielabittencourt00@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkcamp@lists.libreplanetbr.org \
--cc=outreachy-kernel@googlegroups.com \
--cc=rdunlap@infradead.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=teddy.wang@siliconmotion.com \
--cc=trivial@kernel.org \
/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
Powered by JetHome