From: Paul Bolle <pebolle@tiscali.nl>
To: Markos Chandras <markos.chandras@imgtec.com>
Cc: Valentin Rothberg <valentinrothberg@gmail.com>,
Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org, linux-kernel@vger.kernel.org
Subject: MIPS: FP32XX_HYBRID_FPRS
Date: Sat, 14 Feb 2015 17:57:02 +0100 [thread overview]
Message-ID: <1423933022.9418.8.camel@x220> (raw)
Your d8fb6537f1d4 ("MIPS: kernel: elf: Improve the overall ABI and FPU
mode checks") is included in yesterday's linux-next (ie, next-20150213).
I noticed because a script I use to check linux-next spotted a minor
problem with it.
That commit removed the only user of Kconfig symbol FP32XX_HYBRID_FPRS.
Setting FP32XX_HYBRID_FPRS is now pointless in linux-next. Is the
trivial commit to its entry form arch/mips/Kconfig.debug queued
somewhere?
Paul Bolle
next reply other threads:[~2015-02-14 16:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-14 16:57 Paul Bolle [this message]
2015-02-14 17:33 ` MIPS: FP32XX_HYBRID_FPRS Paul Bolle
2015-02-16 8:44 ` Markos Chandras
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=1423933022.9418.8.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=markos.chandras@imgtec.com \
--cc=ralf@linux-mips.org \
--cc=valentinrothberg@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).