[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210422075645.GA5996@alpha.franken.de>
Date: Thu, 22 Apr 2021 09:56:45 +0200
From: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To: "Maciej W. Rozycki" <macro@...am.me.uk>
Cc: "H. Nikolaus Schaller" <hns@...delico.com>,
Arnd Bergmann <arnd@...db.de>,
Huacai Chen <chenhuacai@...nel.org>,
Huacai Chen <chenhuacai@...ngson.cn>,
Jiaxun Yang <jiaxun.yang@...goat.com>,
linux-arch@...r.kernel.org, linux-mips@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 4/4] MIPS: Avoid DIVU in `__div64_32' is result would be
zero
On Wed, Apr 21, 2021 at 06:16:18PM +0200, Maciej W. Rozycki wrote:
> On Wed, 21 Apr 2021, H. Nikolaus Schaller wrote:
>
> > > We already check the high part of the divident against zero to avoid the
> >
> > nit-picking: s/divident/dividend/
>
> Umm, I find this embarassing (and I hesitated reaching for a dictionary
> to double-check the spelling!). Indeed why would this be different from
> subtrahend or minuend?
>
> Thomas, as this mistake has spread across three out of these patches,
> both in change descriptions and actual code, would you mind dropping the
> series from mips-next altogether and I'll respin the series with all
> these issues corrected?
I'm sorry, but I don't rebase mips-next and the patches have been pushed
out before I received this mail.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
Powered by blists - more mailing lists