From: kernel test robot <lkp@intel.com>
To: Dragos Tatulea <dtatulea@nvidia.com>
Cc: stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH] vdpa/mlx5: Fix crash on shutdown for when no ndev exists
Date: Thu, 27 Jul 2023 03:10:30 +0800 [thread overview]
Message-ID: <ZMFvpmbXmk176Dy7@c507f7d2ae6a> (raw)
In-Reply-To: <20230726190744.14143-1-dtatulea@nvidia.com>
Hi,
Thanks for your patch.
FYI: kernel test robot notices the stable kernel rule is not satisfied.
Rule: 'Cc: stable@vger.kernel.org' or 'commit <sha1> upstream.'
Subject: [PATCH] vdpa/mlx5: Fix crash on shutdown for when no ndev exists
Link: https://lore.kernel.org/stable/20230726190744.14143-1-dtatulea%40nvidia.com
The check is based on https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-07-26 19:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 19:07 [PATCH] vdpa/mlx5: Fix crash on shutdown for when no ndev exists Dragos Tatulea
2023-07-26 19:07 ` Dragos Tatulea via Virtualization
2023-07-26 19:10 ` kernel test robot [this message]
2023-07-26 19:26 ` Michael S. Tsirkin
2023-07-26 19:26 ` Michael S. Tsirkin
2023-07-27 16:02 ` Dragos Tatulea
2023-07-27 16:02 ` Dragos Tatulea via Virtualization
2023-07-27 16:28 ` Michael S. Tsirkin
2023-07-27 16:28 ` Michael S. Tsirkin
2023-07-31 7:15 ` Dragos Tatulea
2023-07-31 7:15 ` Dragos Tatulea via Virtualization
2023-07-31 9:08 ` Michael S. Tsirkin
2023-07-31 9:08 ` Michael S. Tsirkin
2023-08-01 3:59 ` Jason Wang
2023-08-01 3:59 ` Jason Wang
2023-08-01 8:17 ` Dragos Tatulea
2023-08-01 8:17 ` Dragos Tatulea via Virtualization
2023-08-02 2:51 ` Jason Wang
2023-08-02 2:51 ` Jason Wang
2023-08-02 7:56 ` Dragos Tatulea
2023-08-02 7:56 ` Dragos Tatulea via Virtualization
2023-08-03 15:02 ` Dragos Tatulea
2023-08-03 15:02 ` Dragos Tatulea via Virtualization
2023-08-03 15:12 ` Michael S. Tsirkin
2023-08-03 15:12 ` Michael S. Tsirkin
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=ZMFvpmbXmk176Dy7@c507f7d2ae6a \
--to=lkp@intel.com \
--cc=dtatulea@nvidia.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.