public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Bityutskiy, Artem" <artem.bityutskiy@intel.com>
To: Fubo Chen <fubo.chen@gmail.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH] mtd: Fix memory leak triggered by removal
Date: Fri, 9 Mar 2012 09:48:33 +0000	[thread overview]
Message-ID: <1331286668.22872.51.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1331286547.22872.49.camel@sauron.fi.intel.com>

On Fri, 2012-03-09 at 11:49 +0200, Artem Bityutskiy wrote:
> Please, provide better explanation in the commit message about which
> problem you solve, why you do this, and how you tested this.
> blktrans_dev_release() also calls blk_cleanup_queue() - why we need to
> do it 2 times?

Sorry, you told which problem you solve, but still, could you please
provide more invormation about why the problem existed and when it it
was triggered, and how you fix this and why this fix is correct.

-- 
Best Regards,
Artem Bityutskiy
---------------------------------------------------------------------
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki 
Business Identity Code: 0357606 - 4 
Domiciled in Helsinki 

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

      reply	other threads:[~2012-03-09  9:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-25 16:57 [PATCH] mtd: Fix memory leak triggered by removal Fubo Chen
2012-03-09  9:49 ` Artem Bityutskiy
2012-03-09  9:48   ` Bityutskiy, Artem [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=1331286668.22872.51.camel@sauron.fi.intel.com \
    --to=artem.bityutskiy@intel.com \
    --cc=dwmw2@infradead.org \
    --cc=fubo.chen@gmail.com \
    --cc=linux-mtd@lists.infradead.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