From: Guenter Roeck <linux@roeck-us.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Huang Pei <huangpei@loongson.cn>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-kernel <linux-kernel@vger.kernel.org>,
Stable <stable@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Shuah Khan <shuah@kernel.org>,
patches@kernelci.org, lkft-triage@lists.linaro.org,
Pavel Machek <pavel@denx.de>,
Jonathan Hunter <jonathanh@nvidia.com>,
Florian Fainelli <f.fainelli@gmail.com>,
slade@sladewatkins.com
Subject: Re: [PATCH 5.15 000/256] 5.15.27-rc2 review
Date: Tue, 8 Mar 2022 14:45:50 -0800 [thread overview]
Message-ID: <ab0b668c-e321-e1d9-3cc3-a609111b828d@roeck-us.net> (raw)
In-Reply-To: <YifFMPFMp9gPnjPc@kroah.com>
On 3/8/22 13:05, Greg Kroah-Hartman wrote:
> On Tue, Mar 08, 2022 at 11:08:10PM +0530, Naresh Kamboju wrote:
[ ... ]
>>>
>>> Reverting 4778338032b3 ("MIPS: fix local_{add,sub}_return on MIPS64")
>>> has fixed all the 3 build failures.
>>
>> MIPS: fix local_{add,sub}_return on MIPS64
>> [ Upstream commit 277c8cb3e8ac199f075bf9576ad286687ed17173 ]
>>
>> Use "daddu/dsubu" for long int on MIPS64 instead of "addu/subu"
>>
>> Fixes: 7232311ef14c ("local_t: mips extension")
>> Signed-off-by: Huang Pei <huangpei@loongson.cn>
>> Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
>> Signed-off-by: Sasha Levin <sashal@kernel.org>
>
> Ah, I'll queue up the revert for that in the morning, thanks for finding
> it. Odd it doesn't trigger the same issue in 5.16.y.
>
If you don't want to revert: the fix needs the following two patches:
e5b40668e93 ("slip: fix macro redefine warning")
b81e0c2372e ("block: drop unused includes in <linux/genhd.h>")
Both are in v5.16, so you won't see the problem there.
Guenter
next prev parent reply other threads:[~2022-03-08 23:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 16:28 Greg Kroah-Hartman
2022-03-07 19:41 ` Florian Fainelli
2022-03-07 23:49 ` Shuah Khan
[not found] ` <CADo9pHjuByLte3d8WhKf1jWw_=EoW-76405ptW-sZg0-AakxqQ@mail.gmail.com>
[not found] ` <CADo9pHiJGXFwvXDRqRCjYqowJkkP3GYzkO8jqPQK=z71V_5FOw@mail.gmail.com>
2022-03-08 15:48 ` Greg Kroah-Hartman
2022-03-08 2:31 ` Fox Chen
2022-03-08 7:49 ` Naresh Kamboju
2022-03-08 9:06 ` Ron Economos
2022-03-08 13:35 ` Bagas Sanjaya
2022-03-08 15:36 ` Sudip Mukherjee
2022-03-08 16:09 ` Sudip Mukherjee
2022-03-08 17:38 ` Naresh Kamboju
2022-03-08 21:05 ` Greg Kroah-Hartman
2022-03-08 22:27 ` Sudip Mukherjee
2022-03-09 0:53 ` Guenter Roeck
2022-03-09 9:53 ` Sudip Mukherjee
2022-03-09 11:58 ` Greg Kroah-Hartman
2022-03-08 22:45 ` Guenter Roeck [this message]
2022-03-09 11:57 ` Greg Kroah-Hartman
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=ab0b668c-e321-e1d9-3cc3-a609111b828d@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=huangpei@loongson.cn \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=patches@kernelci.org \
--cc=pavel@denx.de \
--cc=shuah@kernel.org \
--cc=slade@sladewatkins.com \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=tsbogend@alpha.franken.de \
/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
all inboxes | Powered by JetHome®