From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V4 1/5] of: Implement managed of_iomap()
Date: Mon, 16 Apr 2012 14:42:38 +0000 [thread overview]
Message-ID: <201204161442.38725.arnd@arndb.de> (raw)
In-Reply-To: <6a0872f9d8959bc9d66d179e4911d6f09a219b42.1334548272.git.viresh.kumar@st.com>
On Monday 16 April 2012, Viresh Kumar wrote:
> This simplifies cleanup paths of user code by providing managed version of
> of_iomap().
>
> Signed-off-by: Viresh Kumar <viresh.kumar@st.com>
> Cc: Grant Likely <grant.likely@secretlab.ca>
This one looks good,
Acked-by: Arnd Bergmann <arnd@arndb.de>
but I wonder if we should also have a devm_of_request_and_ioremap
(maybe with a shorter name) that combines this with request_resource.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Viresh Kumar <viresh.kumar@st.com>
Cc: devicetree-discuss@ozlabs.org, swarren@wwwdotorg.org,
linus.walleij@linaro.org, spear-devel@list.st.com,
Rob Herring <rob.herring@calxeda.com>,
Grant Likely <grant.likely@secretlab.ca>,
viresh.linux@gmail.com, olof@lixom.net,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V4 1/5] of: Implement managed of_iomap()
Date: Mon, 16 Apr 2012 14:42:38 +0000 [thread overview]
Message-ID: <201204161442.38725.arnd@arndb.de> (raw)
In-Reply-To: <6a0872f9d8959bc9d66d179e4911d6f09a219b42.1334548272.git.viresh.kumar@st.com>
On Monday 16 April 2012, Viresh Kumar wrote:
> This simplifies cleanup paths of user code by providing managed version of
> of_iomap().
>
> Signed-off-by: Viresh Kumar <viresh.kumar@st.com>
> Cc: Grant Likely <grant.likely@secretlab.ca>
This one looks good,
Acked-by: Arnd Bergmann <arnd@arndb.de>
but I wonder if we should also have a devm_of_request_and_ioremap
(maybe with a shorter name) that combines this with request_resource.
Arnd
next prev parent reply other threads:[~2012-04-16 14:42 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 4:13 [PATCH V4 0/5] pinctrl: Add SPEAr pinctrl support Viresh Kumar
2012-04-16 4:13 ` Viresh Kumar
2012-04-16 4:13 ` [PATCH V4 1/5] of: Implement managed of_iomap() Viresh Kumar
2012-04-16 4:13 ` Viresh Kumar
2012-04-16 9:27 ` Linus Walleij
2012-04-16 9:27 ` Linus Walleij
2012-04-16 14:42 ` Arnd Bergmann [this message]
2012-04-16 14:42 ` Arnd Bergmann
2012-04-16 15:06 ` Grant Likely
2012-04-16 15:06 ` Grant Likely
2012-04-16 15:12 ` viresh kumar
2012-04-16 15:19 ` Grant Likely
2012-04-16 15:19 ` Grant Likely
2012-04-16 16:21 ` viresh kumar
2012-04-16 16:21 ` viresh kumar
2012-04-16 17:06 ` Grant Likely
2012-04-16 17:06 ` Grant Likely
[not found] ` <CACxGe6t9+M5jQKkRduup7_wk4SKYu1SuTz7wzf0MEvo0poojRw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-04-16 17:10 ` viresh kumar
2012-04-16 17:33 ` Sergei Shtylyov
2012-04-16 17:33 ` Sergei Shtylyov
2012-04-16 4:13 ` [PATCH V4 2/5] SPEAr: Remove existing padmux support for SPEAr Viresh Kumar
2012-04-16 4:13 ` Viresh Kumar
2012-04-16 4:13 ` [PATCH V4 3/5] pinctrl: Add SPEAr pinctrl drivers Viresh Kumar
2012-04-16 4:13 ` Viresh Kumar
2012-04-17 8:32 ` Viresh Kumar
2012-04-17 8:32 ` Viresh Kumar
2012-04-18 11:24 ` Linus Walleij
2012-04-18 11:24 ` Linus Walleij
2012-04-16 4:14 ` [PATCH V4 5/5] SPEAr3xx: Add pinctrl support for boards Viresh Kumar
2012-04-16 4:14 ` Viresh Kumar
2012-04-16 9:29 ` [PATCH V4 0/5] pinctrl: Add SPEAr pinctrl support Linus Walleij
2012-04-16 9:29 ` Linus Walleij
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=201204161442.38725.arnd@arndb.de \
--to=arnd@arndb.de \
--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.