From: kernel test robot <lkp@intel.com>
To: Philipp Stanner <pstanner@redhat.com>
Cc: stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v5 2/5] lib: move pci_iomap.c to drivers/pci/
Date: Wed, 13 Dec 2023 18:51:10 +0800 [thread overview]
Message-ID: <ZXmMnhe3YpLOqYam@171f04e7aea4> (raw)
In-Reply-To: <20231213104922.13894-3-pstanner@redhat.com>
Hi,
Thanks for your patch.
FYI: kernel test robot notices the stable kernel rule is not satisfied.
The check is based on https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html#option-1
Rule: add the tag "Cc: stable@vger.kernel.org" in the sign-off area to have the patch automatically included in the stable tree.
Subject: [PATCH v5 2/5] lib: move pci_iomap.c to drivers/pci/
Link: https://lore.kernel.org/stable/20231213104922.13894-3-pstanner%40redhat.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-12-13 10:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 10:49 [PATCH v5 0/5] Regather scattered PCI-Code Philipp Stanner
2023-12-13 10:49 ` [PATCH v5 1/5] lib/pci_iomap.c: fix cleanup bugs in pci_iounmap() Philipp Stanner
2023-12-13 10:49 ` [PATCH v5 2/5] lib: move pci_iomap.c to drivers/pci/ Philipp Stanner
2023-12-13 10:51 ` kernel test robot [this message]
2023-12-13 10:49 ` [PATCH v5 3/5] lib: move pci-specific devres code " Philipp Stanner
2023-12-13 10:49 ` [PATCH v5 4/5] pci: move devres code from pci.c to devres.c Philipp Stanner
2023-12-13 10:49 ` [PATCH v5 5/5] lib, pci: unify generic pci_iounmap() Philipp Stanner
-- strict thread matches above, loose matches on Subject: below --
2024-01-04 9:07 [PATCH v5 RESEND 0/5] Regather scattered PCI-Code Philipp Stanner
2024-01-04 9:07 ` [PATCH v5 2/5] lib: move pci_iomap.c to drivers/pci/ Philipp Stanner
2024-01-04 9:08 ` kernel test robot
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=ZXmMnhe3YpLOqYam@171f04e7aea4 \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pstanner@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox