public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Ron Economos <re@w6rz.net>,
	stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Cc: kernel test robot <lkp@intel.com>
Subject: Re: [PATCH 6.1] Partial revert of xhci: use pm_ptr() instead #ifdef for CONFIG_PM conditionals
Date: Sat, 18 Jan 2025 15:52:08 +0100	[thread overview]
Message-ID: <2025011849-graffiti-swung-a8ec@gregkh> (raw)
In-Reply-To: <Z4ud2ua6GrwqaaBl@9bc2624f7252>

On Sat, Jan 18, 2025 at 08:26:02PM +0800, kernel test robot wrote:
> 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-3
> 
> Rule: The upstream commit ID must be specified with a separate line above the commit text.
> Subject: [PATCH 6.1] Partial revert of xhci: use pm_ptr() instead #ifdef for CONFIG_PM conditionals
> Link: https://lore.kernel.org/stable/20250118122409.4052121-1-re%40w6rz.net
> 
> Please ignore this mail if the patch is not relevant for upstream.

Ron, don't worry about this, it's a false-positive.



  reply	other threads:[~2025-01-18 14:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-18 12:24 [PATCH 6.1] Partial revert of xhci: use pm_ptr() instead #ifdef for CONFIG_PM conditionals Ron Economos
2025-01-18 12:26 ` kernel test robot
2025-01-18 14:52   ` Greg KH [this message]
2025-01-18 14:51 ` Greg Kroah-Hartman
2025-01-18 19:41 ` Sasha Levin
2025-01-19  7:37 ` Greg Kroah-Hartman
  -- strict thread matches above, loose matches on Subject: below --
2025-01-18 12:15 Ron Economos
2025-01-18 12:18 ` kernel test robot
2025-01-18 19:40 ` Sasha Levin

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=2025011849-graffiti-swung-a8ec@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=re@w6rz.net \
    --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