From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: shaozhengchao <shaozhengchao@huawei.com>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
Leon Romanovsky <leonro@nvidia.com>,
Paolo Abeni <pabeni@redhat.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.15 000/131] 5.15.79-rc1 review
Date: Tue, 15 Nov 2022 14:59:27 +0100 [thread overview]
Message-ID: <Y3ObPwyWx4bEAoAt@kroah.com> (raw)
In-Reply-To: <f0136268-63d4-66ec-98fe-b7584b388906@huawei.com>
On Tue, Nov 15, 2022 at 11:34:12AM +0800, shaozhengchao wrote:
>
>
> On 2022/11/15 10:56, Naresh Kamboju wrote:
> > On Mon, 14 Nov 2022 at 18:24, Greg Kroah-Hartman
> > <gregkh@linuxfoundation.org> wrote:
> > >
> > > This is the start of the stable review cycle for the 5.15.79 release.
> > > There are 131 patches in this series, all will be posted as a response
> > > to this one. If anyone has any issues with these being applied, please
> > > let me know.
> > >
> > > Responses should be made by Wed, 16 Nov 2022 12:44:21 +0000.
> > > Anything received after that time might be too late.
> > >
> > > The whole patch series can be found in one patch at:
> > > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.15.79-rc1.gz
> > > or in the git tree and branch at:
> > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.15.y
> > > and the diffstat can be found below.
> > >
> > > thanks,
> > >
> > > greg k-h
> >
> > As others reported,
> > arm: allmodconfig failed [1] due to following warnings / errors.
> >
> > drivers/net/ethernet/mediatek/mtk_star_emac.c: In function 'mtk_star_enable':
> > drivers/net/ethernet/mediatek/mtk_star_emac.c:980:22: error: 'struct
> > mtk_star_priv' has no member named 'rx_napi'; did you mean 'napi'?
> > 980 | napi_disable(&priv->rx_napi);
> > | ^~~~~~~
> > | napi
> > drivers/net/ethernet/mediatek/mtk_star_emac.c:981:22: error: 'struct
> > mtk_star_priv' has no member named 'tx_napi'; did you mean 'napi'?
> > 981 | napi_disable(&priv->tx_napi);
> > | ^~~~~~~
> > | napi
> >
> >
> > ---
> > net: ethernet: mtk-star-emac: disable napi when connect and start PHY
> > failed in mtk_star_enable()
> > [ Upstream commit b0c09c7f08c2467b2089bdf4adb2fbbc2464f4a8 ]
> >
> >
> > [1] https://builds.tuxbuild.com/2HXmwUDUvmWI1Uc7zsdXNcsTqW1/
> >
> > --
> > Linaro LKFT
> > https://lkft.linaro.org
>
> Yes ,For stable-5.10, commit 0a8bd81fd6aaace14979152e0540da8ff158a00a
> ("net: ethernet: mtk-star-emac: separate tx/rx handling with two NAPIs")
> is not merged. So, please use napi_disable(&priv->napi) instead of
> napi_disable(&priv->rx_napi) and napi_disable(&priv->tx_napi).
I think you mean 5.15 here, not 5.10, right?
Can you send a properly backported version of this commit for 5.10.y and
5.15.y so that I can queue it up? I'll go drop this offending one from
the queue now and push out a -rc2 so that it doesn't stall the release.
thanks,
greg k-h
next prev parent reply other threads:[~2022-11-15 13:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 12:44 [PATCH 5.15 000/131] 5.15.79-rc1 review Greg Kroah-Hartman
2022-11-14 17:52 ` Jon Hunter
2022-11-14 19:26 ` Guenter Roeck
2022-11-15 14:04 ` Greg Kroah-Hartman
2022-11-14 20:19 ` Shuah Khan
2022-11-14 21:06 ` Slade Watkins
2022-11-14 22:04 ` Florian Fainelli
2022-11-15 0:14 ` Guenter Roeck
2022-11-15 2:02 ` Kelsey Steele
2022-11-15 2:56 ` Naresh Kamboju
2022-11-15 3:34 ` shaozhengchao
2022-11-15 13:59 ` Greg Kroah-Hartman [this message]
2022-11-15 14:04 ` Greg Kroah-Hartman
2022-11-15 4:03 ` Bagas Sanjaya
2022-11-15 7:29 ` Ron Economos
2022-11-15 10:49 ` Sudip Mukherjee
2022-11-15 14:04 ` Greg Kroah-Hartman
2022-11-15 12:02 ` Naresh Kamboju
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=Y3ObPwyWx4bEAoAt@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=f.fainelli@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=pabeni@redhat.com \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=sashal@kernel.org \
--cc=shaozhengchao@huawei.com \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.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