[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210422110855.GA9564@alpha.franken.de>
Date: Thu, 22 Apr 2021 13:08:55 +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 Thu, Apr 22, 2021 at 11:12:40AM +0200, Maciej W. Rozycki wrote:
> On Thu, 22 Apr 2021, Thomas Bogendoerfer wrote:
>
> > > 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.
>
> Hmm, what about changes known to actually break something then? Like
> with R6 here? Those will undoubtedly cause someone a headache with
> bisection sometime in the future. Are you sure your policy is the best
> possible?
This is my Linus pull tree, so I'm following
Documentation/maintainer/rebasing-and-merging.rst
> Meanwhile I'll be able to give DECstation figures only. I guess such
> limited results will suffice if I post the fix as an update rather than
> replacement.
thank you.
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