Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Anders Roxell <anders.roxell@linaro.org>
Cc: stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [backport PATCH 1/2] tools perf: Fix compilation error with new binutils
Date: Mon, 17 Apr 2023 20:31:03 +0800	[thread overview]
Message-ID: <ZD08B1j+Ps5D/pkd@96b608206aa4> (raw)
In-Reply-To: <20230417122943.2155502-2-anders.roxell@linaro.org>

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: [backport PATCH 1/2] tools perf: Fix compilation error with new binutils
Link: https://lore.kernel.org/stable/20230417122943.2155502-2-anders.roxell%40linaro.org

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

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




  reply	other threads:[~2023-04-17 12:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-17 12:29 [backport PATCH 0/2] stable v5.15, v5.10 and v5.4: fix perf build errors Anders Roxell
2023-04-17 12:29 ` [backport PATCH 1/2] tools perf: Fix compilation error with new binutils Anders Roxell
2023-04-17 12:31   ` kernel test robot [this message]
2023-04-17 17:14   ` Ian Rogers
2023-04-18 16:43     ` Quentin Monnet
2023-04-18 18:04       ` Ian Rogers
2023-04-17 12:29 ` [backport PATCH 2/2] tools build: Add feature test for init_disassemble_info API changes Anders Roxell
2023-04-17 17:18 ` [backport PATCH 0/2] stable v5.15, v5.10 and v5.4: fix perf build errors Ian Rogers
2023-04-18  9:04 ` Greg KH
2023-04-20 18:24   ` Anders Roxell
2023-04-20 20:34     ` Ian Rogers

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=ZD08B1j+Ps5D/pkd@96b608206aa4 \
    --to=lkp@intel.com \
    --cc=anders.roxell@linaro.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