From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Silviu Popescu <silviupopescu1990@gmail.com>
Cc: Zhang Rui <rui.zhang@intel.com>,
andrew@lunn.ch, jason@lakedaemon.net, rob.lee@linaro.org,
len.brown@intel.com, khilman@ti.com, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kirkwood: fix coccicheck warnings
Date: Fri, 22 Mar 2013 01:43:39 +0100 [thread overview]
Message-ID: <1794203.BzriCauSp9@vostro.rjw.lan> (raw)
In-Reply-To: <CAPWTe+J4kduwxEgqMrKuZE48NMRzqYzeRUWXJMAmp4Dw=aEGtg@mail.gmail.com>
On Friday, March 22, 2013 02:18:38 AM Silviu Popescu wrote:
> On Fri, Mar 22, 2013 at 1:48 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > On Monday, March 11, 2013 09:35:19 AM Silviu-Mihai Popescu wrote:
> >> Convert all uses of devm_request_and_ioremap() to the newly introduced
> >> devm_ioremap_resource() which provides more consistent error handling.
> >>
> >> devm_ioremap_resource() provides its own error messages so all explicit
> >> error messages can be removed from the failure code paths.
> >>
> >> Signed-off-by: Silviu-Mihai Popescu <silviupopescu1990@gmail.com>
> >
> > If I'm supposed to take these changes, please split them into separate patches
> > for cpufreq, cpuidle and thermal (which would be for Rui BTW).
>
> There seems to be an existing patch for thermal[1], as Rui pointed out himself.
> I have split the changes in two patches, as you have requested, and resent them.
>
> [1] http://marc.info/?l=linux-pm&m=136238017027514&w=2
Thanks a lot!
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
prev parent reply other threads:[~2013-03-22 0:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 7:35 [PATCH] kirkwood: fix coccicheck warnings Silviu-Mihai Popescu
2013-03-11 7:56 ` Andrew Lunn
2013-03-11 13:46 ` Jason Cooper
2013-03-11 13:49 ` Viresh Kumar
2013-03-11 14:55 ` Zhang Rui
2013-03-11 17:03 ` Rafael J. Wysocki
2013-03-11 17:02 ` Silviu Popescu
2013-03-11 23:58 ` Zhang Rui
2013-03-12 0:10 ` Rafael J. Wysocki
2013-03-21 23:48 ` Rafael J. Wysocki
2013-03-22 0:18 ` Silviu Popescu
2013-03-22 0:43 ` Rafael J. Wysocki [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=1794203.BzriCauSp9@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=andrew@lunn.ch \
--cc=jason@lakedaemon.net \
--cc=khilman@ti.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rob.lee@linaro.org \
--cc=rui.zhang@intel.com \
--cc=silviupopescu1990@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox