From: kernel test robot <lkp@intel.com>
To: Hsin-Yi Wang <hsinyi@chromium.org>
Cc: stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v6 5/5] drm/panel-edp: Avoid adding multiple preferred modes
Date: Wed, 8 Nov 2023 04:49:33 +0800 [thread overview]
Message-ID: <ZUqi3YUBSGTJwBhF@b4d6968193cf> (raw)
In-Reply-To: <20231107204611.3082200-6-hsinyi@chromium.org>
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 v6 5/5] drm/panel-edp: Avoid adding multiple preferred modes
Link: https://lore.kernel.org/stable/20231107204611.3082200-6-hsinyi%40chromium.org
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2023-11-07 20:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 20:41 [PATCH v6 0/5] Add a few panels and use correct modes Hsin-Yi Wang
2023-11-07 20:41 ` [PATCH v6 1/5] drm/panel-edp: drm/panel-edp: Fix AUO B116XAK01 name and timing Hsin-Yi Wang
2023-11-08 15:35 ` Maxime Ripard
2023-11-10 0:17 ` Doug Anderson
2023-11-07 20:41 ` [PATCH v6 2/5] drm/panel-edp: drm/panel-edp: Fix AUO B116XTN02 name Hsin-Yi Wang
2023-11-08 15:35 ` Maxime Ripard
2023-11-10 0:18 ` Doug Anderson
2023-11-07 20:41 ` [PATCH v6 3/5] drm/panel-edp: drm/panel-edp: Add several generic edp panels Hsin-Yi Wang
2023-11-07 20:57 ` Greg KH
2023-11-07 21:52 ` Hsin-Yi Wang
2023-11-08 15:36 ` Maxime Ripard
2023-11-07 20:41 ` [PATCH v6 4/5] drm/panel-edp: Add override_edid_mode quirk for generic edp Hsin-Yi Wang
2023-11-07 20:58 ` Greg KH
2023-11-08 15:45 ` Maxime Ripard
2023-11-08 17:04 ` Doug Anderson
2023-11-07 20:41 ` [PATCH v6 5/5] drm/panel-edp: Avoid adding multiple preferred modes Hsin-Yi Wang
2023-11-07 20:49 ` kernel test robot [this message]
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=ZUqi3YUBSGTJwBhF@b4d6968193cf \
--to=lkp@intel.com \
--cc=hsinyi@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