mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Daniel Ngu <daniel.dy.ngu@gmail.com>
Cc: Jonathan Kim <jonathankim@gctsemi.com>,
	Dean ahn <deanahn@gctsemi.com>,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: gdm724x: gdm_lte.c: fixed coding style
Date: Sun, 16 Mar 2014 12:24:36 -0700	[thread overview]
Message-ID: <1394997876.5689.60.camel@joe-AO722> (raw)
In-Reply-To: <20140316192025.GE3478@quad>

On Mon, 2014-03-17 at 08:20 +1300, Daniel Ngu wrote:
> Line over 80 characters
> Unchecked sscanf return value
[]
> diff --git a/drivers/staging/gdm724x/gdm_lte.c b/drivers/staging/gdm724x/gdm_lte.c
[]
> @@ -536,7 +567,8 @@ static u8 find_dev_index(u32 nic_type)
>  	return index;
>  }
>  
> -static void gdm_lte_netif_rx(struct net_device *dev, char *buf, int len, int flagged_nic_type)
> +static void gdm_lte_netif_rx(struct net_device *dev, char *buf, int len,
> +			     int flagged_nic_type)
>  {
>  	u32 nic_type;
>  	struct nic *nic;
> @@ -551,28 +583,41 @@ static void gdm_lte_netif_rx(struct net_device *dev, char *buf, int len, int fla
[]
>  			struct dhcp_packet {

This one would be better fixed by moving the struct definition
out of this function altogether.

>  				u8 op;      /* BOOTREQUEST or BOOTREPLY */
> -				u8 htype;   /* hardware address type. 1 = 10mb ethernet */
> +				u8 htype;   /* hardware address type.
> +					       1 = 10mb ethernet */
>  				u8 hlen;    /* hardware address length */
>  				u8 hops;    /* used by relay agents only */
>  				u32 xid;    /* unique id */
> -				u16 secs;   /* elapsed since client began acquisition/renewal */
> +				u16 secs;   /* elapsed since client began
> +					       acquisition/renewal */
>  				u16 flags;  /* only one flag so far: */
> -				#define BROADCAST_FLAG 0x8000 /* "I need broadcast replies" */
> -				u32 ciaddr; /* client IP (if client is in BOUND, RENEW or REBINDING state) */
> +				#define BROADCAST_FLAG 0x8000 /* "I need
> +								 broadcast
> +								 replies" */
> +				u32 ciaddr; /* client IP (if client is in
> +					       BOUND, RENEW or REBINDING
> +					       state) */
>  				u32 yiaddr; /* 'your' (client) IP address */
> -				/* IP address of next server to use in bootstrap, returned in DHCPOFFER, DHCPACK by server */
> +				/* IP address of next server to use in
> +				 * bootstrap, returned in DHCPOFFER, DHCPACK by
> +				 * server */
>  				u32 siaddr_nip;
>  				u32 gateway_nip; /* relay agent IP address */
> -				u8 chaddr[16];   /* link-layer client hardware address (MAC) */
> +				u8 chaddr[16];   /* link-layer client hardware
> +						    address (MAC) */
>  				u8 sname[64];    /* server host name (ASCIZ) */
>  				u8 file[128];    /* boot file name (ASCIZ) */
> -				u32 cookie;      /* fixed first four option bytes (99,130,83,99 dec) */
> +				u32 cookie;      /* fixed first four option
> +						    bytes (99,130,83,99 dec) */
>  			} __packed;




  reply	other threads:[~2014-03-16 19:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-16 19:20 Daniel Ngu
2014-03-16 19:24 ` Joe Perches [this message]
2014-03-16 19:31   ` Joe Perches

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=1394997876.5689.60.camel@joe-AO722 \
    --to=joe@perches.com \
    --cc=daniel.dy.ngu@gmail.com \
    --cc=deanahn@gctsemi.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=jonathankim@gctsemi.com \
    --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

all inboxes | Powered by JetHome®