linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: Joshua Kinard <kumba@gentoo.org>,
	Stephen Zhang <starzhangzsd@gmail.com>,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] MIPS: Remove incorrect `cpu_has_fpu' overrides
Date: Wed, 4 May 2022 22:28:08 +0200	[thread overview]
Message-ID: <20220504202808.GA23391@alpha.franken.de> (raw)
In-Reply-To: <alpine.DEB.2.21.2205012307310.9383@angie.orcam.me.uk>

On Sun, May 01, 2022 at 11:14:11PM +0100, Maciej W. Rozycki wrote:
> Hi,
> 
>  Forcing `cpu_has_fpu' to 1 is unsupported as it breaks the `nofpu' kernel 
> parameter and more recently also the CONFIG_MIPS_FP_SUPPORT configuration 
> option.  Remove the broken `cpu_has_fpu' overrides then for IP27 and IP30 
> systems.
> 
>  This v3 of the series adds credit to Stephen for reporting the issue,
> which I forgot on previous iterations.
> 
>  Please apply.

series applied to mips-next.

Thomas.

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

      parent reply	other threads:[~2022-05-04 20:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-01 22:14 [PATCH v3 0/2] MIPS: Remove incorrect `cpu_has_fpu' overrides Maciej W. Rozycki
2022-05-01 22:14 ` [PATCH v3 1/2] MIPS: IP27: Remove incorrect `cpu_has_fpu' override Maciej W. Rozycki
2022-05-01 22:14 ` [PATCH v3 2/2] MIPS: IP30: " Maciej W. Rozycki
2022-05-04 20:28 ` 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=20220504202808.GA23391@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=kumba@gentoo.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=macro@orcam.me.uk \
    --cc=starzhangzsd@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).