All of lore.kernel.org
 help / color / mirror / Atom feed
From: philipp.muhoray@gmail.com (Philipp Muhoray)
To: kernelnewbies@lists.kernelnewbies.org
Subject: [PATCH] staging: Check for Null return of allocated skb in fw_download_code
Date: Wed, 13 Aug 2014 20:09:29 +0200	[thread overview]
Message-ID: <53EBA9D9.6020605@gmail.com> (raw)
In-Reply-To: <CAPDOMVh3mWRikT6P8L=1Cg6tR2ez8LFXW5StUG9XSEd_4aT5BQ@mail.gmail.com>


Am 2014-08-13 20:03, schrieb Nick Krause:
> On Wed, Aug 13, 2014 at 12:55 PM, Nick Krause <xerofoify@gmail.com> wrote:
>> On Wed, Aug 13, 2014 at 12:02 PM,  <Valdis.Kletnieks@vt.edu> wrote:
>>> On Wed, 13 Aug 2014 18:50:43 +0400, Max Filippov said:
>>>
>>>> No need to trigger it, faking it would be enough, e.g.:
>>>> +                if (++i < 3)
>>>> +                        skb  = dev_alloc_skb(frag_length + 4);
>>>> +                else
>>>> +                        skb = NULL;
>>> Don't bet on this triggering on a real system without some additional
>>> scaffolding - take a look at what the function is doing, and ask yourself
>>> how many times it will be called on the average system :)
>> Seems to be called a lot. In addition I can only build test this as I
>> don't have the hardware.
>> Cheers Nick
>
> 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]);
> I am wondering how do I fix this, I will attach my patch so I can fix
> this out and send a proper patch :).
> By the way thanks for the help guys :).
> Nick
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
This error indicates that you are using a function that is not yet known 
to the compiler. Check if there's a prototype or function definition 
BEFORE it's actual use.

br,
phil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140813/02b2ac73/attachment.html 

  reply	other threads:[~2014-08-13 18:09 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 [this message]
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
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=53EBA9D9.6020605@gmail.com \
    --to=philipp.muhoray@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 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.