From: Ido Schimmel <idosch@idosch.org>
To: Denis Kirjanov <dkirjanov@suse.de>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
jiri@nvidia.com, mlxsw@nvidia.com,
Danielle Ratson <danieller@nvidia.com>,
Eric Biederman <ebiederm@xmission.com>,
Ido Schimmel <idosch@nvidia.com>
Subject: Re: [PATCH net-next 2/2] mlxsw: pci: Add shutdown method in PCI driver
Date: Tue, 23 Nov 2021 11:15:08 +0200 [thread overview]
Message-ID: <YZyxHPsiWMYdAkb2@shredder> (raw)
In-Reply-To: <34c443a5-c36b-2a16-adda-222da6dc5238@suse.de>
On Tue, Nov 23, 2021 at 11:47:34AM +0300, Denis Kirjanov wrote:
>
>
> 11/23/21 10:54 AM, Ido Schimmel пишет:
> > From: Danielle Ratson <danieller@nvidia.com>
> >
> > On an arm64 platform with the Spectrum ASIC, after loading and executing
> > a new kernel via kexec, the following trace [1] is observed. This seems
> > to be caused by the fact that the device is not properly shutdown before
> > executing the new kernel.
>
> This should be sent to net tree instead of net-next with Fixes tag added.
This is not a regression (never worked) and the system does not crash.
The trace is only observed on a specific platform and only with kexec
which I assume nobody is using but our team (for development purposes).
Therefore, I prefer to route it via net-next. If users complain
(unlikely), I will send backports to stable kernels.
next prev parent reply other threads:[~2021-11-23 9:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 7:54 [PATCH net-next 0/2] mlxsw: Various updates Ido Schimmel
2021-11-23 7:54 ` [PATCH net-next 1/2] mlxsw: spectrum_router: Remove deadcode in mlxsw_sp_rif_mac_profile_find Ido Schimmel
2021-11-23 7:54 ` [PATCH net-next 2/2] mlxsw: pci: Add shutdown method in PCI driver Ido Schimmel
2021-11-23 8:47 ` Denis Kirjanov
2021-11-23 9:15 ` Ido Schimmel [this message]
2021-11-23 11:50 ` [PATCH net-next 0/2] mlxsw: Various updates patchwork-bot+netdevbpf
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=YZyxHPsiWMYdAkb2@shredder \
--to=idosch@idosch.org \
--cc=danieller@nvidia.com \
--cc=davem@davemloft.net \
--cc=dkirjanov@suse.de \
--cc=ebiederm@xmission.com \
--cc=idosch@nvidia.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).