public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: d binderman <dcb314@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RE: Linux kernel 2.6.33-rc5 bug report
Date: Mon, 25 Jan 2010 20:21:37 -0800	[thread overview]
Message-ID: <20100126042137.GA31666@suse.de> (raw)
In-Reply-To: <BLU108-W259018EFE8CC5014C4C1829C5F0@phx.gbl>

On Mon, Jan 25, 2010 at 10:16:55AM +0000, d binderman wrote:
> 
> 
> Hello there,
> 
> Greg wrote:
> > Care to make up a patch to fix this issue? 
> 
> Here is an untested trivial patch to fix a memory leak in Linux kernel
> 2.6.33-rc5 directory drivers/staging/otus
> 
> From:  David Binderman <dcb314@hotmail.com>
> 
> Fix memory leak in drivers/staging/otus
> 
> Signed-off-by: David Binderman <dcb314@hotmail.com>
> 
> ---
> 
> 
> --- drivers/staging/otus/ioctl.c.sav??? 2010-01-25 09:45:30.000000000 +0000
> +++ drivers/staging/otus/ioctl.c??????? 2010-01-25 09:55:56.000000000 +0000
> @@ -866,15 +866,15 @@ int usbdrvwext_giwscan(struct net_device
> ??????? char *current_ev = extra;
> ??????? char *end_buf;
> ??????? int i;
> -?????? /* struct zsBssList BssList; */
> -?????? struct zsBssListV1 *pBssList = kmalloc(sizeof(struct zsBssListV1),
> -?????????????????????????????????????????????????????????????? GFP_KERNEL);
> ??????? /* BssList = wd->sta.pBssList; */

Very wierd characters here, can you attach the patch instead?

thanks,

greg k-h

      reply	other threads:[~2010-01-26  4:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BLU108-W6FFE536027D1D0125666D9C600@phx.gbl>
     [not found] ` <20100125060850.GA23232@suse.de>
2010-01-25 10:16   ` [PATCH] RE: Linux kernel 2.6.33-rc5 bug report d binderman
2010-01-26  4:21     ` 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=20100126042137.GA31666@suse.de \
    --to=gregkh@suse.de \
    --cc=dcb314@hotmail.com \
    --cc=linux-kernel@vger.kernel.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