From: Samuel Ortiz <sameo@linux.intel.com>
To: Julia Lawall <julia@diku.dk>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers/mfd/timberdale.c: clean up error handling code
Date: Mon, 22 Aug 2011 12:24:02 +0200 [thread overview]
Message-ID: <20110822102402.GM4607@sortiz-mobl> (raw)
In-Reply-To: <1312966036-15896-1-git-send-email-julia@diku.dk>
Hi Julia,
On Wed, Aug 10, 2011 at 10:47:16AM +0200, Julia Lawall wrote:
> From: Julia Lawall <julia@diku.dk>
>
> In the first three cases, ioremap has been called, so iounmap is needed. A
> new label for this is introduced, to differentiate it from err_msix, which
> is the first point at which msix_entries actually needs to be freed.
Thanks a lot, patch applied.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
WARNING: multiple messages have this Message-ID (diff)
From: Samuel Ortiz <sameo@linux.intel.com>
To: Julia Lawall <julia@diku.dk>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers/mfd/timberdale.c: clean up error handling code
Date: Mon, 22 Aug 2011 10:24:02 +0000 [thread overview]
Message-ID: <20110822102402.GM4607@sortiz-mobl> (raw)
In-Reply-To: <1312966036-15896-1-git-send-email-julia@diku.dk>
Hi Julia,
On Wed, Aug 10, 2011 at 10:47:16AM +0200, Julia Lawall wrote:
> From: Julia Lawall <julia@diku.dk>
>
> In the first three cases, ioremap has been called, so iounmap is needed. A
> new label for this is introduced, to differentiate it from err_msix, which
> is the first point at which msix_entries actually needs to be freed.
Thanks a lot, patch applied.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2011-08-22 10:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 8:47 [PATCH] drivers/mfd/timberdale.c: clean up error handling code Julia Lawall
2011-08-10 8:47 ` Julia Lawall
2011-08-22 10:24 ` Samuel Ortiz [this message]
2011-08-22 10:24 ` Samuel Ortiz
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=20110822102402.GM4607@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=julia@diku.dk \
--cc=kernel-janitors@vger.kernel.org \
--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 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.