All of lore.kernel.org
 help / color / mirror / Atom feed
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_CPU_MIPS_R6?
Date: Sat, 14 Feb 2015 18:26:45 +0100	[thread overview]
Message-ID: <1423934805.9418.23.camel@x220> (raw)

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

             reply	other threads:[~2015-02-14 17:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-14 17:26 Paul Bolle [this message]
2015-02-15  1:23 ` MIPS: CONFIG_CPU_MIPS_R6? Leonid Yegoshin
2015-02-15  1:23   ` Leonid Yegoshin
2015-02-16  7:46 ` Markos Chandras
2015-02-16  7:46   ` 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=1423934805.9418.23.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.