From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [pci:for-linus 3/3] checkpatch: ERROR: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit d5af729dc207 ("PCI: Mark NVIDIA T4 GPUs to avoid bus reset")'
Date: Sat, 9 Sep 2023 07:59:29 +0800 [thread overview]
Message-ID: <202309090714.bKAaUPKQ-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "checkpatch"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
CC: linux-pci@vger.kernel.org
TO: Bjorn Helgaas <helgaas@kernel.org>
INFO skip CC for checkpatch warnings
tree: https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git for-linus
head: 5260bd6d36c83c5b269c33baaaf8c78e520908b0
commit: 5260bd6d36c83c5b269c33baaaf8c78e520908b0 [3/3] Revert "PCI: Mark NVIDIA T4 GPUs to avoid bus reset"
:::::: branch date: 4 hours ago
:::::: commit date: 4 hours ago
reproduce: (https://download.01.org/0day-ci/archive/20230909/202309090714.bKAaUPKQ-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/r/202309090714.bKAaUPKQ-lkp@intel.com/
# many are suggestions rather than must-fix
ERROR: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit d5af729dc207 ("PCI: Mark NVIDIA T4 GPUs to avoid bus reset")'
#8:
d5af729dc207 ("PCI: Mark NVIDIA T4 GPUs to avoid bus reset") avoided
ERROR: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit d5af729dc207 ("PCI: Mark NVIDIA T4 GPUs to avoid bus reset")'
#16:
Revert d5af729dc207 as requested by Wu Zongyong. This will leave SBR
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-09-08 23:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202309090714.bKAaUPKQ-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@lists.linux.dev \
/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.