From: Paul Burton <paul.burton@imgtec.com>
To: Nick Krause <xerofoify@gmail.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
John Crispin <blogic@openwrt.org>, <markos.chandras@imgtec.com>,
<Steven.Hill@imgtec.com>, Linux-MIPS <linux-mips@linux-mips.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: smp-cmp.c: CDFIXMES
Date: Wed, 23 Jul 2014 07:46:57 +0100 [thread overview]
Message-ID: <20140723064657.GK30558@pburton-laptop> (raw)
In-Reply-To: <CAPDOMVjNyAwo53Coz8MFuUs70M7j1e3QWprus5vGpTfAw=hspg@mail.gmail.com>
On Wed, Jul 23, 2014 at 12:40:59AM -0400, Nick Krause wrote:
> Are the lines with CDFIXME still needed? If not please tell me as I
> will send in a patch removing these
> two from this file in order to help you guys out :).
> Cheers Nick
Hi Nick,
I imagine the only answer any of us can give you is "we don't know". If
we did then we'd have removed the code or the comments already.
Please do note that the smp-cmp.c file lives behind a Kconfig option
that is now marked as deprecated, and that there is other work going on
in areas related to clocksource & clock events on the applicable
systems. So whilst someone could spend the time figuring out whether
those lines are useful, I expect that cleaning up these old FIXMEs is
not a particularly high priority for anyone right now.
If you'll leave them alone for a while I expect they'll disappear one
way or another in a few cycles time, along with the rest of the file.
Thanks,
Paul
next prev parent reply other threads:[~2014-07-23 6:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 4:40 Nick Krause
2014-07-23 6:46 ` Paul Burton [this message]
2014-07-23 15:19 ` Nick Krause
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=20140723064657.GK30558@pburton-laptop \
--to=paul.burton@imgtec.com \
--cc=Steven.Hill@imgtec.com \
--cc=blogic@openwrt.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=markos.chandras@imgtec.com \
--cc=ralf@linux-mips.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
all inboxes | Powered by JetHome®