public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesper Juhl <jesper.juhl@gmail.com>
To: Abhay Salunke <Abhay_Salunke@dell.com>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [RFC][patch 2.6.14-rc2] dell_rbu: Changing packet update mechanism
Date: Thu, 29 Sep 2005 02:00:36 +0200	[thread overview]
Message-ID: <200509290200.37203.jesper.juhl@gmail.com> (raw)
In-Reply-To: <20050923194009.GA2682@littleblue.us.dell.com>

On Friday 23 September 2005 21:40, Abhay Salunke wrote:
> Please ignore earlier patches as there was error submitting it! :-(
> patch below is good...
> 

Ok, I'm being pedantic. So shoot me.
There are a few tiny bits CodingStyle wise that could be better. No big deal,
I'm nitpicking in the extreme here...


[snip]
> -	pr_debug("fill_last_packet: entry \n");

	pr_debug("fill_last_packet: entry\n");


[snip]
> -	pr_debug("fill_last_packet: exit \n");

	pr_debug("fill_last_packet: exit\n");


[snip]
>  	pr_debug("create_packet: exit \n");

	pr_debug("create_packet: exit\n");


[snip]
> +	temp = (u8 *) data;

	temp = (u8 *)data;


[snip]
> +do_packet_read(char *data, struct list_head *ptemp_list,
>  	int length, int bytes_read, int *list_read_count)

Hmm, I believe the prefered style for functions is to indent parameters that
won't fit on the first line by two tab stops, like this : 

do_packet_read(char *data, struct list_head *ptemp_list,
		int length, int bytes_read, int *list_read_count)

There are several occourences of this.


[snip]
> +packet_read_list(char *data, size_t * pread_length)

packet_read_list(char *data, size_t *pread_length)

[snip]
>   * img_update_free: Frees the buffer allocated for storing BIOS image
>   * Always called with lock held and returned with lock held

 * Always called with lock held and returned with lock held.


[snip]
> +	.attr = {.name = "data",.owner = THIS_MODULE,.mode = 0444},

	.attr = {.name = "data", .owner = THIS_MODULE, .mode = 0444},


[snip]
> +	.attr = {.name = "image_type",.owner = THIS_MODULE,.mode = 0644},

	.attr = {.name = "image_type", .owner = THIS_MODULE, .mode = 0644},


[snip]
> +	.attr = {.name = "packet_size",.owner = THIS_MODULE,.mode = 0644},

	.attr = {.name = "packet_size", .owner = THIS_MODULE, .mode = 0644},



-- 
Jesper Juhl <jesper.juhl@gmail.com>



  reply	other threads:[~2005-09-28 23:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-23 19:40 [RFC][patch 2.6.14-rc2] dell_rbu: Changing packet update mechanism Abhay Salunke
2005-09-29  0:00 ` Jesper Juhl [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-09-29  2:27 Abhay_Salunke
2005-09-29  2:36 ` Jesper Juhl
2005-09-23 19:33 Abhay Salunke

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=200509290200.37203.jesper.juhl@gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=Abhay_Salunke@dell.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.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