kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: xerofoify@gmail.com (nick)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Bug Patch
Date: Mon, 08 Sep 2014 20:51:10 -0400	[thread overview]
Message-ID: <540E4EFE.8010508@gmail.com> (raw)
In-Reply-To: <75027.1410214199@turing-police.cc.vt.edu>



On 14-09-08 06:09 PM, Valdis.Kletnieks at vt.edu wrote:
> On Mon, 08 Sep 2014 17:05:39 -0400, nick said:
> 
>> In ieee_80211_rx.c we may have a Null allocated sub in parse_subframe
>> and need to check if the allocated skb is NUll. If it is return -ENOMEM.
> 
>> +			if (!sub_skb)
>> +				return NULL;
> 
> 1) null, Null, and NULL are all OK in various contexts.  NUll isn't.
> 
> 2) the rest of the file uses 'return 0;' not 'return NULL;'
> 
> Oh, and (3)  What's wrong with this picture?
> 
> Nick, this is *exactly* the reason why *NOBODY* wants to accept code
> from you.  It's faster and more efficient for me to code the
> patch myself and stick a Reported-By: crediting you for spotting
> the bug than it takes for multiple iterations to get your patch right.
> 
> And the *reason* I'm submitting the patch myself is because every single
> problem that's been pointed out to you with this patch is something that
> has been pointed out to you before on other patches.
> 
> 
> 
> 
> 
> 
Thanks for at least giving me credit.
Nick 

      reply	other threads:[~2014-09-09  0:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-08 10:36 Bug Patch nick
2014-09-08 11:10 ` Sudip Mukherjee
2014-09-08 11:21 ` Tobias S. Josefowitz
2014-09-08 11:35   ` Sudip Mukherjee
2014-09-08 12:45     ` Doug Wilson
2014-09-08 18:08 ` Valdis.Kletnieks at vt.edu
2014-09-08 21:05   ` nick
2014-09-08 22:09     ` Valdis.Kletnieks at vt.edu
2014-09-09  0:51       ` nick [this message]

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=540E4EFE.8010508@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).