From: Chase Southwood <chase.southwood@yahoo.com>
To: Levente Kurusa <levex@linux.com>
Cc: Ian Abbott <abbotti@mev.co.uk>,
H Hartley Sweeten <hsweeten@visionengravers.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
OSUOSL Drivers <devel@driverdev.osuosl.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: comedi: fix memory leak
Date: Sat, 15 Mar 2014 00:21:29 -0700 (PDT) [thread overview]
Message-ID: <1394868089.38574.YahooMailNeo@web164001.mail.gq1.yahoo.com> (raw)
In-Reply-To: <5323F944.2040400@linux.com>
>On Saturday, March 15, 2014 1:55 AM, Levente Kurusa <levex@linux.com> wrote:
>>On 03/15/2014 04:30 AM, Chase Southwood wrote:
>>> On Friday, March 14, 2014 11:47 AM, Levente Kurusa <levex@linux.com> wrote:
>>>
>>>Call kfree() on bdev. The variable is otherwise leaked.
>>>
>>>Signed-off-by: Levente Kurusa <levex@linux.com>
>>>[...]
>>>
>>
>>
>>Levente,
>>
>>This change has already been made in staging-next (by me, actually :) ). In
>>order to avoid re-doing work which has already been done, please make sure to base
>>all of your patches off of linux-next (or for staging, staging-next).
>>
>>Thanks,
>>Chase
>>
>
>Ah, yes I see now. I wonder how it didn't reach my tree.
>Anyways, thanks for the heads up!
>
>--
>Regards,
>Levente Kurusa
No problem, just wanted to make sure you were working from an up-to-date tree :)
Thanks,
Chase
prev parent reply other threads:[~2014-03-15 7:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 16:16 Levente Kurusa
2014-03-15 3:30 ` Chase Southwood
2014-03-15 6:55 ` Levente Kurusa
2014-03-15 7:21 ` Chase Southwood [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=1394868089.38574.YahooMailNeo@web164001.mail.gq1.yahoo.com \
--to=chase.southwood@yahoo.com \
--cc=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hsweeten@visionengravers.com \
--cc=levex@linux.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
all inboxes | Powered by JetHome®