public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: kernel test robot <lkp@intel.com>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	oe-kbuild-all@lists.linux.dev, Len Brown <lenb@kernel.org>,
	Josh Law <objecting@objecting.org>,
	kees@kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH v1 1/1] ACPI: processor: idle: Replace strlcat() with better alternative
Date: Tue, 17 Mar 2026 10:29:27 +0200	[thread overview]
Message-ID: <abkQ5-TPZgrdwlAV@ashevche-desk.local> (raw)
In-Reply-To: <202603170957.D9ZQ5sVR-lkp@intel.com>

On Tue, Mar 17, 2026 at 09:17:56AM +0100, kernel test robot wrote:
> Hi Andy,
> 
> kernel test robot noticed the following build warnings:
> 
> [auto build test WARNING on rafael-pm/linux-next]
> [also build test WARNING on rafael-pm/bleeding-edge linus/master v7.0-rc4 next-20260316]
> [If your patch is applied to the wrong git tree, kindly drop us a note.
> And when submitting patch, we suggest to use '--base' as documented in
> https://git-scm.com/docs/git-format-patch#_base_tree_information]
> 
> url:    https://github.com/intel-lab-lkp/linux/commits/Andy-Shevchenko/ACPI-processor-idle-Replace-strlcat-with-better-alternative/20260317-014800
> base:   https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
> patch link:    https://lore.kernel.org/r/20260316170158.1596857-1-andriy.shevchenko%40linux.intel.com
> patch subject: [PATCH v1 1/1] ACPI: processor: idle: Replace strlcat() with better alternative
> config: x86_64-rhel-9.4 (https://download.01.org/0day-ci/archive/20260317/202603170957.D9ZQ5sVR-lkp@intel.com/config)
> compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260317/202603170957.D9ZQ5sVR-lkp@intel.com/reproduce)
> 
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202603170957.D9ZQ5sVR-lkp@intel.com/

Yes, thanks, I already sent a v2 before getting this report.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2026-03-17  8:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-16 17:01 [PATCH v1 1/1] ACPI: processor: idle: Replace strlcat() with better alternative Andy Shevchenko
2026-03-16 18:43 ` Josh Law
2026-03-16 18:47   ` Andy Shevchenko
2026-03-16 18:49     ` Josh Law
2026-03-16 19:42       ` Andy Shevchenko
2026-03-16 19:51         ` Josh Law
2026-03-17  8:17 ` kernel test robot
2026-03-17  8:29   ` Andy Shevchenko [this message]
2026-03-20 19:17 ` Kees Cook
2026-03-20 19:25   ` Andy Shevchenko
2026-03-20 19:26     ` Kees Cook
2026-03-20 19:31     ` Josh Law
2026-03-20 19:39       ` Andy Shevchenko
2026-03-20 19:34     ` Kees Cook
2026-03-20 19:39       ` Andy Shevchenko

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=abkQ5-TPZgrdwlAV@ashevche-desk.local \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=kees@kernel.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=objecting@objecting.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=rafael.j.wysocki@intel.com \
    /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