From: Paul Bolle <pebolle@tiscali.nl>
To: Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>
Cc: Valentin Rothberg <valentinrothberg@gmail.com>,
Markos Chandras <markos.chandras@imgtec.com>,
Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org, linux-kernel@vger.kernel.org
Subject: MIPS: CONFIG_MIPS_R6?
Date: Sat, 14 Feb 2015 18:21:09 +0100 [thread overview]
Message-ID: <1423934469.9418.18.camel@x220> (raw)
Your commits 430857eae56c ("MIPS: mm: Add MIPS R6 instruction
encodings") and 90163242784b ("MIPS: kernel: unaligned: Add support for
the MIPS R6") are included in yesterday's linux-next (ie,
next-20150213). I noticed because a script I use to check linux-next
spotted a problem with it.
These commits added three references to CONFIG_MIPS_R6, were probably
CONFIG_CPU_MIPSR6 was intended. One reference is in a comment, which
should be trivial to get fixed. The other two references are in
(negative) preprocessor checks. It's not certain, at least not to me,
how these should be fixed.
Paul Bolle
next reply other threads:[~2015-02-14 17:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-14 17:21 Paul Bolle [this message]
2015-02-15 1:22 ` MIPS: CONFIG_MIPS_R6? Leonid Yegoshin
2015-02-16 8:39 ` Paul Bolle
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=1423934469.9418.18.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=Leonid.Yegoshin@imgtec.com \
--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).