From: jszhang@marvell.com (Jisheng Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/4] clk: mvebu: add missing iounmap
Date: Sat, 24 Aug 2013 11:53:42 +0800 [thread overview]
Message-ID: <20130824115342.675b3a6b@xhacker> (raw)
In-Reply-To: <20130823212950.8231.90154@quantum>
Hi Mike,
On Fri, 23 Aug 2013 14:29:50 -0700
Mike Turquette <mturquette@linaro.org> wrote:
> Quoting Jisheng Zhang (2013-08-22 19:34:01)
> > Add missing iounmap to setup error path.
> >
> > Change-Id: I4371569d14d7026aa9f90d7cd53f669d365fe26a
>
> Please remove Change-Id's from the commit message for upstream patch
> submissions in the future. I can remove this one, this time.
>
> I've taken the patch into clk-next.
>
Thanks for kindly reminding. I'll take care of this in the future.
Best Regards,
Jisheng
WARNING: multiple messages have this Message-ID (diff)
From: Jisheng Zhang <jszhang@marvell.com>
To: Mike Turquette <mturquette@linaro.org>
Cc: "jason@lakedaemon.net" <jason@lakedaemon.net>,
"andrew@lunn.ch" <andrew@lunn.ch>,
"gregory.clement@free-electrons.com"
<gregory.clement@free-electrons.com>,
"thomas.petazzoni@free-electrons.com"
<thomas.petazzoni@free-electrons.com>,
"ezequiel.garcia@free-electrons.com"
<ezequiel.garcia@free-electrons.com>,
"sebastian.hesselbarth@gmail.com"
<sebastian.hesselbarth@gmail.com>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 3/4] clk: mvebu: add missing iounmap
Date: Sat, 24 Aug 2013 11:53:42 +0800 [thread overview]
Message-ID: <20130824115342.675b3a6b@xhacker> (raw)
In-Reply-To: <20130823212950.8231.90154@quantum>
Hi Mike,
On Fri, 23 Aug 2013 14:29:50 -0700
Mike Turquette <mturquette@linaro.org> wrote:
> Quoting Jisheng Zhang (2013-08-22 19:34:01)
> > Add missing iounmap to setup error path.
> >
> > Change-Id: I4371569d14d7026aa9f90d7cd53f669d365fe26a
>
> Please remove Change-Id's from the commit message for upstream patch
> submissions in the future. I can remove this one, this time.
>
> I've taken the patch into clk-next.
>
Thanks for kindly reminding. I'll take care of this in the future.
Best Regards,
Jisheng
next prev parent reply other threads:[~2013-08-24 3:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 2:33 [PATCH v2 0/4] arm: mvebu: fix resource leak Jisheng Zhang
2013-08-23 2:33 ` Jisheng Zhang
2013-08-23 2:33 ` [PATCH v2 1/4] arm: mvebu: add missing of_node_put() to fix reference leak Jisheng Zhang
2013-08-23 2:33 ` Jisheng Zhang
2013-08-23 2:34 ` [PATCH v2 2/4] bus: " Jisheng Zhang
2013-08-23 2:34 ` Jisheng Zhang
2013-08-23 2:34 ` [PATCH v2 3/4] clk: mvebu: add missing iounmap Jisheng Zhang
2013-08-23 2:34 ` Jisheng Zhang
2013-08-23 21:29 ` Mike Turquette
2013-08-23 21:29 ` Mike Turquette
2013-08-24 3:53 ` Jisheng Zhang [this message]
2013-08-24 3:53 ` Jisheng Zhang
2013-08-23 2:34 ` [PATCH v2 4/4] pinctrl: mvebu: Convert to use devm_ioremap_resource Jisheng Zhang
2013-08-23 2:34 ` Jisheng Zhang
2013-08-24 15:06 ` Ezequiel Garcia
2013-08-24 15:06 ` Ezequiel Garcia
2013-08-26 9:59 ` Jisheng Zhang
2013-08-26 9:59 ` Jisheng Zhang
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=20130824115342.675b3a6b@xhacker \
--to=jszhang@marvell.com \
--cc=linux-arm-kernel@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 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.