All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Sudeep Dutt <sudeep.dutt@intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org, "Dixit,
	Ashutosh" <ashutosh.dixit@intel.com>
Subject: Re: [PATCH char-misc-next 4/4] misc: mic: use common error path
Date: Wed, 6 Jan 2016 17:36:08 +0530	[thread overview]
Message-ID: <20160106120608.GA28646@sudip-pc> (raw)
In-Reply-To: <1449888385.93285.547.camel@localhost>

On Fri, Dec 11, 2015 at 06:46:25PM -0800, Sudeep Dutt wrote:
> On Mon, 2015-11-23 at 17:24 +0530, Sudip Mukherjee wrote:
> > Instead of calling release_firmware() on every error and then jumping
> > lets have a common release_firmware() in the error path.
> > This patch also fixes a memory leak where we missed release_firmware()
> > if mic_x100_load_command_line() fails.
> > 
> 
> Thanks for this patch series Sudip. All 4 patches look good.
> 
> Reviewed-by: Sudeep Dutt <sudeep.dutt@intel.com>

Hi Greg,
If your tree is not yet closed then a gentle ping for this series.

regards
sudip

      reply	other threads:[~2016-01-06 12:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-23 11:54 [PATCH char-misc-next 1/4] misc: mic: remove unneeded debug message Sudip Mukherjee
2015-11-23 11:54 ` [PATCH char-misc-next 2/4] misc: mic: return error properly Sudip Mukherjee
2015-11-23 11:54 ` [PATCH char-misc-next 3/4] misc: mic: return error directly Sudip Mukherjee
2015-11-23 11:54 ` [PATCH char-misc-next 4/4] misc: mic: use common error path Sudip Mukherjee
2015-12-12  2:46   ` Sudeep Dutt
2016-01-06 12:06     ` Sudip Mukherjee [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=20160106120608.GA28646@sudip-pc \
    --to=sudipm.mukherjee@gmail.com \
    --cc=ashutosh.dixit@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sudeep.dutt@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.