From: Nishanth Menon <nm@ti.com>
To: Viresh Kumar <viresh.kumar@linaro.org>, nick <xerofoify@gmail.com>
Cc: Kevin Hilman <khilman@deeprootsystems.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-omap <linux-omap@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: FIX ME in omap-cpufreq.c
Date: Fri, 5 Dec 2014 07:20:32 -0600 [thread overview]
Message-ID: <5481B120.9050109@ti.com> (raw)
In-Reply-To: <CAKohpomfgZEkQ4Nv_VqtUe9ObveB+Ymw2Q0KxJLLZmkzHbQEQg@mail.gmail.com>
On 12/04/2014 10:30 PM, Viresh Kumar wrote:
> On 4 December 2014 at 23:13, nick <xerofoify@gmail.com> wrote:
>> Greetings Kevin and the other maintainers of this file,
>
> Hi,
>
>> I am wondering why the below code still has a fix me? It seems rather trivial to fix, as all we need is the transition
>> time of the CPU. Due to this and I don't have the hardware do any of you have the hardware, can any of you tell me the
>> correct value for this if you have this hardware. Further more I will paste the code below.
>
> Not every FIXME wants to get fixed. Believe me.
>
> Don't just grep for FIXME's in kernel and send patches for that. It
> isn't working anymore Nick.
>
> I understand that you want to get some name for yourself in the kernel community
> (and for sure there is nothing wrong in that), but the way you have chosen isn't
> taking you there. People aren't really happy with the way things are proceeding.
>
> If you really want to help kernel (and yourself), start getting deeper
> knowledge of
> frameworks you have any idea of. And they try to solve some real problems.
>
> I don't want to discourage you here, but trying to show the right path. Rest is
> upon you :)
>
by the way, the file is redundant once we get omap3 platforms to be DT
only and will be deleted. It is meant only for legacy boot for OMAP3
at the moment.
--
Regards,
Nishanth Menon
prev parent reply other threads:[~2014-12-05 13:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54809D3F.6070108@gmail.com>
2014-12-05 4:30 ` FIX ME in omap-cpufreq.c Viresh Kumar
2014-12-05 13:20 ` Nishanth Menon [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=5481B120.9050109@ti.com \
--to=nm@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.org \
--cc=xerofoify@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;
as well as URLs for NNTP newsgroup(s).