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
On 02/14/2015 09:26 AM, 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
>
Yes, please.
- Leonid.
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