From: Markos Chandras <markos.chandras@imgtec.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>,
Valentin Rothberg <valentinrothberg@gmail.com>,
Ralf Baechle <ralf@linux-mips.org>, <linux-mips@linux-mips.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: MIPS: CONFIG_CPU_MIPS_R6?
Date: Mon, 16 Feb 2015 07:46:52 +0000 [thread overview]
Message-ID: <20150216074652.GA25858@mchandras-linux.le.imgtec.org> (raw)
In-Reply-To: <1423934805.9418.23.camel@x220>
On Sat, Feb 14, 2015 at 06:26:45PM +0100, Paul Bolle wrote:
> Your commit 33d73a3d4159 ("MIPS: lib: memset: Add MIPS R6 support") is
> included in yesterday's linux next (ie, next-20150213). I noticed
> because a script I use to check linux-next spotted a trivial problem
> with it.
>
> It added a reference to CONFIG_CPU_MIPS_R6 in comment. Should I submit
> the trivial patch to change that into a reference to CONFIG_CPU_MIPSR6
> or do you prefer to do that yourself?
>
>
> Paul Bolle
>
Hi Paul,
Ok thanks I will fix both.
--
markos
prev parent reply other threads:[~2015-02-16 7:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-14 17:26 MIPS: CONFIG_CPU_MIPS_R6? Paul Bolle
2015-02-15 1:23 ` Leonid Yegoshin
2015-02-16 7:46 ` Markos Chandras [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=20150216074652.GA25858@mchandras-linux.le.imgtec.org \
--to=markos.chandras@imgtec.com \
--cc=Leonid.Yegoshin@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=pebolle@tiscali.nl \
--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).