public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Nicholas Krause <xerofoify@gmail.com>
Cc: devel@driverdev.osuosl.org, lisa@xenapiadmin.com,
	ben@decadent.org.uk, valentina.manea.m@gmail.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2] Fixes function fw_download_code to check for Null return from dev_skb_alloc
Date: Tue, 17 Jun 2014 14:57:09 -0700	[thread overview]
Message-ID: <20140617215709.GA20496@kroah.com> (raw)
In-Reply-To: <1403039881-16050-1-git-send-email-xerofoify@gmail.com>

Lots of things wrong here, please step back, and slow down.

Your subject, this really isn't "v2", is it?

On Tue, Jun 17, 2014 at 05:18:01PM -0400, Nicholas Krause wrote:
> Signed-off-by: Nicholas Krause <xerofoify@gmail.com>

You aren't saying what you are doing here in the body of the patch, why
not?

> ---
>  drivers/staging/rtl8192e/rtl8192e/r8192E_firmware.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/staging/rtl8192e/rtl8192e/r8192E_firmware.c b/drivers/staging/rtl8192e/rtl8192e/r8192E_firmware.c
> index 11e915e..e4c8224 100644
> --- a/drivers/staging/rtl8192e/rtl8192e/r8192E_firmware.c
> +++ b/drivers/staging/rtl8192e/rtl8192e/r8192E_firmware.c
> @@ -62,12 +62,14 @@ static bool fw_download_code(struct net_device *dev, u8 *code_virtual_address,
>  
>  		skb  = dev_alloc_skb(frag_length + 4);
>  		if (!skb){
> +			rt_status = false;
> +			return rt_status;
> +		}

Again, this patch will not apply to the tree, you are making it against
your previous patch, which was rejected.  There is no way I can take
this, right?

Please start over and try again from a "clean" kernel tree.

thanks,

greg k-h

      reply	other threads:[~2014-06-17 21:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-17 21:18 [PATCHv2] Fixes function fw_download_code to check for Null return from dev_skb_alloc Nicholas Krause
2014-06-17 21:57 ` Greg KH [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=20140617215709.GA20496@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=ben@decadent.org.uk \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lisa@xenapiadmin.com \
    --cc=valentina.manea.m@gmail.com \
    --cc=xerofoify@gmail.com \
    /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