kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: xerofoify@gmail.com (nick)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Checkpatch Patches
Date: Tue, 16 Sep 2014 09:11:28 -0400	[thread overview]
Message-ID: <54183700.40800@gmail.com> (raw)
In-Reply-To: <20140916130656.GA10530@sudip-PC>



On 14-09-16 09:06 AM, Sudip Mukherjee wrote:
> On Tue, Sep 16, 2014 at 08:44:27AM -0400, nick wrote:
>> I am attaching two check patch patches I wrote in the last few days as I am unable to get a reply 
>> from the maintainers. Would someone please send them off for me.
>> Thanks,
>> Nick 
> 
>> >From 7bf4229fa2f9c4fcf3243bc738c74bfdc58a6594 Mon Sep 17 00:00:00 2001
>> From: Nicholas Krause <xerofoify@gmail.com>
>> Date: Sat, 13 Sep 2014 11:53:24 -0400
>> Subject: [PATCH] staging wlan-ng: Add missing a blank line after declarations
>>
>> Fixing trivial checkpatch warnings about missing line after
>> declarations.
>>
>> Signed-off-by: Nicholas Krause <xerofoify@gmail.com>
>> ---
>> Tested by compilation only.
>>  drivers/staging/wlan-ng/hfa384x.h | 3 +++
>>  1 file changed, 3 insertions(+)
>>
>> diff --git a/drivers/staging/wlan-ng/hfa384x.h b/drivers/staging/wlan-ng/hfa384x.h
>> index 1f2c78c..20d146b 100644
>> --- a/drivers/staging/wlan-ng/hfa384x.h
>> +++ b/drivers/staging/wlan-ng/hfa384x.h
>> @@ -1376,6 +1376,7 @@ int hfa384x_drvr_setconfig(hfa384x_t *hw, u16 rid, void *buf, u16 len);
>>  static inline int hfa384x_drvr_getconfig16(hfa384x_t *hw, u16 rid, void *val)
>>  {
>>  	int result = 0;
>> +
>>  	result = hfa384x_drvr_getconfig(hw, rid, val, sizeof(u16));
>>  	if (result == 0)
>>  		*((u16 *) val) = le16_to_cpu(*((u16 *) val));
>> @@ -1385,6 +1386,7 @@ static inline int hfa384x_drvr_getconfig16(hfa384x_t *hw, u16 rid, void *val)
>>  static inline int hfa384x_drvr_setconfig16(hfa384x_t *hw, u16 rid, u16 val)
>>  {
>>  	u16 value = cpu_to_le16(val);
>> +
>>  	return hfa384x_drvr_setconfig(hw, rid, &value, sizeof(value));
>>  }
>> @@ -1402,6 +1404,7 @@ static inline int
>>  hfa384x_drvr_setconfig16_async(hfa384x_t *hw, u16 rid, u16 val)
>>  {
>>  	u16 value = cpu_to_le16(val);
>> +
>>  	return hfa384x_drvr_setconfig_async(hw, rid, &value, sizeof(value),
>>  					    NULL, NULL);
>>  }
>> 1.9.1
>>
> 
>> >From 5eb3de22f0760ece1e838d48c8dd9148b4331cdc Mon Sep 17 00:00:00 2001
>> From: Nicholas Krause <xerofoify@gmail.com>
>> Date: Mon, 15 Sep 2014 17:07:24 -0400
>> Subject: [PATCH] staging netlogic: Fix checkpatch errors in xlr_net.c
>>
>> This removes the checkpatch errors related to a needed line below
>> declaration of a struct and another about a non nessary printk
>> message about a NULL allocated skb due to the function returning
>> NULL to the caller of the function and the printk no longer being'
>> used or needed by any callers.
>>
> 
> spelling mistakes  
> 
>> Signed-off-by: Nicholas Krause <xerofoify@gmail.com>
>> ---
>>  drivers/staging/netlogic/xlr_net.c | 5 ++---
>>  1 file changed, 2 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/staging/netlogic/xlr_net.c b/drivers/staging/netlogic/xlr_net.c
>> index 9bf407d..28a42831 100644
>> --- a/drivers/staging/netlogic/xlr_net.c
>> +++ b/drivers/staging/netlogic/xlr_net.c
>> @@ -142,10 +142,8 @@ static inline struct sk_buff *xlr_alloc_skb(void)
>>  
>>  	/* skb->data is cache aligned */
>>  	skb = alloc_skb(XLR_RX_BUF_SIZE, GFP_ATOMIC);
>> -	if (!skb) {
>> -		pr_err("SKB allocation failed\n");
> 
> why the error message was removed ? 
> 	
> 
>> +	if (!skb)
>>  		return NULL;
>> -	}
>>  	mac_put_skb_back_ptr(skb);
>>  	return skb;
>>  }
>> @@ -1104,6 +1102,7 @@ err_gmac:
>>  static int xlr_net_remove(struct platform_device *pdev)
>>  {
>>  	struct xlr_net_priv *priv = platform_get_drvdata(pdev);
>> +
>>  	unregister_netdev(priv->ndev);
>>  	mdiobus_unregister(priv->mii_bus);
>>  	mdiobus_free(priv->mii_bus);
>> -- 
>> 1.9.1
>>
> 
> ohhh .. yeah .. and both the patch failed when i tried to apply them to next-20140916
> 
> 
> why are we wasting our time for your patches , which are bound to have some problem ????
> 
> thanks
> sudip
> 
> 
>> _______________________________________________
>> Kernelnewbies mailing list
>> Kernelnewbies at kernelnewbies.org
>> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
> 
I tried these on Greg's tree of staging-next and they worked for me.
Nick

  reply	other threads:[~2014-09-16 13:11 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-16 12:44 Checkpatch Patches nick
2014-09-16 12:47 ` Kristofer Hallin
2014-09-16 12:50   ` nick
2014-09-16 13:06 ` Sudip Mukherjee
2014-09-16 13:11   ` nick [this message]
2014-09-16 13:21     ` Sudip Mukherjee
2014-09-16 13:26       ` nick
     [not found]         ` <CADVatmOZx7q636=b0pQ95CZ93_6jn_jZ2SCPKH7pHmw9P0mRuQ@mail.gmail.com>
     [not found]           ` <54183C0A.80409@gmail.com>
     [not found]             ` <CADVatmP1G1pg-vDmn1z-vg9Ppn7Yhvc=hnhbaOyENbdg6WUO2A@mail.gmail.com>
2014-09-16 13:47               ` Sudip Mukherjee
2014-09-16 13:07 ` Robert P. J. Day
2014-09-16 13:13 ` Robert P. J. Day
2014-09-16 14:19 ` Valdis.Kletnieks at vt.edu
2014-09-16 15:44   ` Nick Krause
2014-09-16 15:50     ` Carlo Caione
2014-09-16 15:57       ` Lidza Louina
2014-09-16 16:08         ` Valdis.Kletnieks at vt.edu
2014-09-16 16:14           ` Robert P. J. Day
2014-09-16 16:11         ` Robert P. J. Day
2014-09-16 16:10     ` Hugo Mills
2014-09-16 16:57     ` Sudip Mukherjee
2014-09-16 17:12       ` Nick Krause
2014-09-16 17:27         ` Robert P. J. Day
2014-09-16 17:27         ` Valdis.Kletnieks at vt.edu
2014-09-16 17:28         ` Rik van Riel
2014-09-16 17:39           ` Valdis.Kletnieks at vt.edu
2014-09-16 18:29             ` Nick Krause
2014-09-16 18:36               ` Kristofer Hallin
2014-09-16 18:44                 ` Rik van Riel
2014-09-16 19:30                   ` Robert P. J. Day
2014-09-16 18:45               ` Mandeep Sandhu

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=54183700.40800@gmail.com \
    --to=xerofoify@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).