Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Matthias Kaehlcke <mka@chromium.org>
Cc: stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v2 1/2] usb: misc: onboard_usb_hub: Don't create platform devices for DT nodes without 'vdd-supply'
Date: Thu, 22 Dec 2022 10:28:08 +0800	[thread overview]
Message-ID: <Y6PAuCsjbX7y3Wrf@416bcb91c936> (raw)
In-Reply-To: <20221222022605.v2.1.If5e7ec83b1782e4dffa6ea759416a27326c8231d@changeid>

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 v2 1/2] usb: misc: onboard_usb_hub: Don't create platform devices for DT nodes without 'vdd-supply'
Link: https://lore.kernel.org/stable/20221222022605.v2.1.If5e7ec83b1782e4dffa6ea759416a27326c8231d%40changeid

The check is based on https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp




  parent reply	other threads:[~2022-12-22  2:28 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-22  2:26 [PATCH v2 1/2] usb: misc: onboard_usb_hub: Don't create platform devices for DT nodes without 'vdd-supply' Matthias Kaehlcke
2022-12-22  2:26 ` [PATCH v2 2/2] usb: misc: onboard_hub: Fail silently when there is no platform device Matthias Kaehlcke
2022-12-22  5:50   ` Greg Kroah-Hartman
2022-12-22 12:21   ` Stefan Wahren
2022-12-22  2:28 ` kernel test robot [this message]
2022-12-22  5:50 ` [PATCH v2 1/2] usb: misc: onboard_usb_hub: Don't create platform devices for DT nodes without 'vdd-supply' Greg Kroah-Hartman
2022-12-22 12:19 ` Stefan Wahren
2022-12-22 19:26 ` Doug Anderson
2022-12-23  7:46   ` Icenowy Zheng
2023-01-02  9:20     ` Alexander Stein
2023-01-02 11:44       ` Stefan Wahren
2023-01-02 14:38         ` Alexander Stein
2023-01-03 17:31           ` Matthias Kaehlcke
2023-01-03 17:24     ` Matthias Kaehlcke
2023-01-03 17:12   ` Matthias Kaehlcke
2023-01-04  9:00     ` Alexander Stein
2023-01-04 19:37       ` Matthias Kaehlcke
2023-01-05  1:42         ` Matthias Kaehlcke
2023-01-05  7:50         ` Stefan Wahren
2023-01-05 19:41           ` Matthias Kaehlcke
2023-01-05 20:45         ` Matthias Kaehlcke
2022-12-23 14:01 ` Johan Hovold
2023-01-03 17:42   ` Matthias Kaehlcke

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=Y6PAuCsjbX7y3Wrf@416bcb91c936 \
    --to=lkp@intel.com \
    --cc=mka@chromium.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox