All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu (Valdis.Kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: [PATCH] staging: Check for Null return of allocated skb in fw_download_code
Date: Wed, 13 Aug 2014 15:17:19 -0400	[thread overview]
Message-ID: <16587.1407957439@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Wed, 13 Aug 2014 14:03:08 -0400." <CAPDOMVh3mWRikT6P8L=1Cg6tR2ez8LFXW5StUG9XSEd_4aT5BQ@mail.gmail.com>

On Wed, 13 Aug 2014 14:03:08 -0400, Nick Krause said:

> I did test my patch by doing a kernel build and I get this error,
> drivers/staging/rtl8192e/rtl8192e/r8192E_firmware.c:66:4: error:
> implicit declaration of function ???skb_quene_purge???
> [-Werror=implicit-function-declaration]
>     skb_quene_purge(&priv->rtllib->skb_waitQ[tcb_desc->queue_index]);

Well, this is a C 101 problem.

> I am wondering how do I fix this,

You fix this by not doing any further kernel hacking until you've gotten
a handle on *VERY BASIC* C development concepts.

Also, you're going to have to justify why you're being a total
dumbass and coding skb_waitQ[tcb_desc->queue_index] when the *obvious*
code is skb_waitQ[TXCMD_QUEUE] - yes, an optimizing compiler will do
that substitution, but code clarity is important.

Argh.  I may have to break out my +5 Trout of Smacking....

On Wed, 13 Aug 2014 15:01:45 -0400, Nick Krause said:
> This is the fixed patch, I do get an error about uninitialized
> variables

Are you *trying* to get put in *everybody's* killfile?

> If someone wants to send this out, please do so as this is has been
> built and applied tested.

And you think that *anybody* wants to upstream a patch from you that even
*you* admit still has trouble??!?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 848 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140813/d83ebb86/attachment.bin 

  parent reply	other threads:[~2014-08-13 19:17 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-13  3:24 [PATCH] staging: Check for Null return of allocated skb in fw_download_code Nicholas Krause
2014-08-13  3:31 ` Nick Krause
2014-08-13  5:35 ` Valdis.Kletnieks at vt.edu
2014-08-13  5:53   ` Manish Katiyar
2014-08-13 13:56     ` Valdis.Kletnieks at vt.edu
2014-08-13 14:50       ` Max Filippov
2014-08-13 16:02         ` Valdis.Kletnieks at vt.edu
2014-08-13 16:55           ` Nick Krause
2014-08-13 18:03             ` Nick Krause
2014-08-13 18:09               ` Philipp Muhoray
2014-08-13 18:11               ` Max Filippov
2014-08-13 18:25                 ` Jerry Snitselaar
2014-08-13 18:27                   ` Nick Krause
2014-08-13 18:58                     ` Nick Krause
2014-08-13 18:20               ` Jeff Haran
2014-08-13 19:17               ` Valdis.Kletnieks at vt.edu [this message]
2014-08-13 19:24                 ` Nick Krause
2014-08-13 19:52                   ` Nick Krause
2014-08-13 19:06             ` Valdis.Kletnieks at vt.edu
  -- strict thread matches above, loose matches on Subject: below --
2014-08-13  3:12 Nicholas Krause
2014-08-13  3:14 ` Nick Krause

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=16587.1407957439@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.