linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Minchan Kim <minchan.kim@gmail.com>
To: Nitin Gupta <ngupta@vflare.org>
Cc: Greg Kroah-Hartman <greg@kroah.com>, linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH] Free memory when create_device is failed
Date: Mon, 11 Jan 2010 17:31:08 +0900	[thread overview]
Message-ID: <28c262361001110031h70e22f56x2b72a5a7813a6900@mail.gmail.com> (raw)
In-Reply-To: <d760cf2d1001110023r17a2ed1as6874f02cfb066d8@mail.gmail.com>

On Mon, Jan 11, 2010 at 5:23 PM, Nitin Gupta <ngupta@vflare.org> wrote:
> Hi Minchan,
>
> On Mon, Jan 11, 2010 at 12:45 PM, Minchan Kim <minchan.kim@gmail.com> wrote:
>>
>>
>> I don't know where I send this patch.
>> Do I send this patch to akpm or only you and LKML?
>>
>
> I think current TO, CC list is okay for this driver.
>
>>
>> If create_device is failed, it can't free gendisk and request_queue
>> of preceding devices. It cause memory leak.
>>
>> This patch fixes it.
>>
>> Signed-off-by: Minchan Kim <minchan.kim@gmail.com>
>> CC: Nitin Gupta <ngupta@vflare.org>
>
>
> FWIW,
> Acked-by: Nitin Gupta <ngupta@vflare.org>

Thanks for the ACK, Nitin. :)



-- 
Kind regards,
Minchan Kim

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2010-01-11  8:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-11  7:15 [PATCH] Free memory when create_device is failed Minchan Kim
2010-01-11  8:23 ` Nitin Gupta
2010-01-11  8:31   ` Minchan Kim [this message]
2010-01-11 15:20 ` Greg KH
2010-01-15  1:36 ` patch staging-ramzswap-free-memory-when-create_device-is-failed.patch added to gregkh-2.6 tree gregkh

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=28c262361001110031h70e22f56x2b72a5a7813a6900@mail.gmail.com \
    --to=minchan.kim@gmail.com \
    --cc=greg@kroah.com \
    --cc=linux-mm@kvack.org \
    --cc=ngupta@vflare.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;
as well as URLs for NNTP newsgroup(s).