From: Lukasz Majewski <l.majewski@samsung.com>
To: Sachin Kamat <sachin.kamat@linaro.org>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: [PATCH 1/1] cpufreq: exynos: Fix compilation warnings
Date: Wed, 27 Nov 2013 08:03:41 +0100 [thread overview]
Message-ID: <20131127080341.71eab132@amdc308.digital.local> (raw)
In-Reply-To: <CAK9yfHws8dkpQzWp2h-xHKvGVzefsXg4FmJM3no0qwnT49n+sA@mail.gmail.com>
Hi Sachin,
> Hi Viresh,
>
> On 19 November 2013 10:29, Viresh Kumar <viresh.kumar@linaro.org>
> wrote:
> > On 19 November 2013 09:53, Sachin Kamat <sachin.kamat@linaro.org>
> > wrote:
> >> Commit a403797bbd81 ("cpufreq: exynos: Convert exynos-cpufreq
> >> to platform driver") forgot to change the function prototype.
> >
> > I can't find this commit anywhere..
>
> > And I can see that you had already given comments for the patch and
> > so this should be fixed right there..
>
> Sorry, please discard this patch. Looks like I had applied this patch
> locally in my tree
> when I was reviewing it. I did give my comments about this warning
> then. Somehow I thought this patch got applied without my comment
> getting addressed, hence I
> fixed this myself. Sorry for the noise.
>
> Lukasz, do you plan to send the updated the patch?
>
Yes. I will sent the update.
--
Best regards,
Lukasz Majewski
Samsung R&D Institute Poland (SRPOL) | Linux Platform Group
prev parent reply other threads:[~2013-11-27 7:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 4:23 [PATCH 1/1] cpufreq: exynos: Fix compilation warnings Sachin Kamat
2013-11-19 4:59 ` Viresh Kumar
2013-11-19 5:07 ` Sachin Kamat
2013-11-27 7:03 ` Lukasz Majewski [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=20131127080341.71eab132@amdc308.digital.local \
--to=l.majewski@samsung.com \
--cc=cpufreq@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=sachin.kamat@linaro.org \
--cc=viresh.kumar@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox