public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Pauli Virtanen <pav@iki.fi>
Cc: stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH] Bluetooth: fix connection setup in l2cap_connect
Date: Sun, 9 Jun 2024 06:03:31 +0800	[thread overview]
Message-ID: <ZmTVM9A3CDRUGKzZ@242c30a86391> (raw)
In-Reply-To: <de9169c3e607696a9430f5beb182c914c136edcf.1717883849.git.pav@iki.fi>

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] Bluetooth: fix connection setup in l2cap_connect
Link: https://lore.kernel.org/stable/de9169c3e607696a9430f5beb182c914c136edcf.1717883849.git.pav%40iki.fi

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki




  reply	other threads:[~2024-06-08 22:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-06 20:46 Bluetooth Kernel Bug: After connecting either HFP/HSP or A2DP is not available (Regression in 6.9.3, 6.8.12) Timo Schröder
2024-06-06 21:23 ` Luiz Augusto von Dentz
2024-06-07  6:10   ` Linux regression tracking (Thorsten Leemhuis)
2024-06-07 21:43     ` Timo Schröder
2024-06-07 22:00       ` Luiz Augusto von Dentz
2024-06-08 12:24         ` Timo Schröder
2024-06-07  3:55 ` Paul Menzel
2024-06-08 12:23   ` Timo Schröder
2024-06-08 21:59 ` [PATCH] Bluetooth: fix connection setup in l2cap_connect Pauli Virtanen
2024-06-08 22:03   ` kernel test robot [this message]
2024-06-09 12:49   ` Timo Schröder
2024-06-09 15:01     ` Pauli Virtanen
     [not found] ` <ad69720e0ba720209cb04240fbc3c5ff059accbc.1717945321.git.pav@iki.fi>
2024-06-09 16:29   ` [PATCH v2] " Timo Schröder

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=ZmTVM9A3CDRUGKzZ@242c30a86391 \
    --to=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=pav@iki.fi \
    --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