linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Wei Li <liwei391@huawei.com>
Cc: Paul Burton <paulburton@kernel.org>,
	Serge Semin <Sergey.Semin@baikalelectronics.ru>,
	Huacai Chen <chenhc@lemote.com>,
	Jiaxun Yang <jiaxun.yang@flygoat.com>,
	Guenter Roeck <linux@roeck-us.net>,
	Ralf Baechle <ralf@linux-mips.org>,
	Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>,
	"Steven J. Hill" <Steven.Hill@imgtec.com>,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
	guohanjun@huawei.com
Subject: Re: [PATCH] MIPS: Add the missing 'CPU_1074K' into __get_cpu_type()
Date: Thu, 24 Sep 2020 15:55:14 +0200	[thread overview]
Message-ID: <20200924135514.GD13973@alpha.franken.de> (raw)
In-Reply-To: <20200923065312.44851-1-liwei391@huawei.com>

On Wed, Sep 23, 2020 at 02:53:12PM +0800, Wei Li wrote:
> Commit 442e14a2c55e ("MIPS: Add 1074K CPU support explicitly.") split
> 1074K from the 74K as an unique CPU type, while it missed to add the
> 'CPU_1074K' in __get_cpu_type(). So let's add it back.
> 
> Fixes: 442e14a2c55e ("MIPS: Add 1074K CPU support explicitly.")
> Signed-off-by: Wei Li <liwei391@huawei.com>
> ---
>  arch/mips/include/asm/cpu-type.h | 1 +
>  1 file changed, 1 insertion(+)

applied to mips-fixes.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

      reply	other threads:[~2020-09-24 13:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-23  6:53 [PATCH] MIPS: Add the missing 'CPU_1074K' into __get_cpu_type() Wei Li
2020-09-24 13:55 ` Thomas Bogendoerfer [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=20200924135514.GD13973@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=Leonid.Yegoshin@imgtec.com \
    --cc=Sergey.Semin@baikalelectronics.ru \
    --cc=Steven.Hill@imgtec.com \
    --cc=chenhc@lemote.com \
    --cc=guohanjun@huawei.com \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=liwei391@huawei.com \
    --cc=paulburton@kernel.org \
    --cc=ralf@linux-mips.org \
    /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).