From: Reinette Chatre <reinette.chatre@intel.com>
To: James Morse <james.morse@arm.com>, kernel test robot <lkp@intel.com>
Cc: <oe-kbuild-all@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
"Borislav Petkov" <bp@suse.de>, Jamie Iles <jamie@nuviainc.com>
Subject: Re: arch/x86/kernel/cpu/resctrl/rdtgroup.c:1196: warning: Function parameter or member 'type' not described in '__rdtgroup_cbm_overlaps'
Date: Wed, 11 Oct 2023 08:41:01 -0700 [thread overview]
Message-ID: <c1eb5dfe-2f0c-43a4-8cf5-3d09d4348a72@intel.com> (raw)
In-Reply-To: <360270f1-8bd8-40de-af54-5527fb1106c9@intel.com>
Hi James,
On 10/10/2023 9:40 AM, Reinette Chatre wrote:
> On 10/10/2023 8:25 AM, James Morse wrote:
>> On 06/10/2023 22:03, kernel test robot wrote:
...
>>> 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/202310070434.mD8eRNAz-lkp@intel.com/
>>
>> I'll float a patch fixing all these - otherwise I get the blame for the whole lot when the
>> code gets moved!
>
> Cleaning this up is already in progress. A fix from Randy addressing a few of the warnings
> has already been merged into x86/urgent and Maciej has a patch ready addressing the rest that
> he will send upstream shortly.
fyi ... Maciej's fix has just been merged to x86/cache.
Reinette
prev parent reply other threads:[~2023-10-11 15:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 21:03 arch/x86/kernel/cpu/resctrl/rdtgroup.c:1196: warning: Function parameter or member 'type' not described in '__rdtgroup_cbm_overlaps' kernel test robot
2023-10-10 15:25 ` James Morse
2023-10-10 16:40 ` Reinette Chatre
2023-10-11 15:41 ` Reinette Chatre [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=c1eb5dfe-2f0c-43a4-8cf5-3d09d4348a72@intel.com \
--to=reinette.chatre@intel.com \
--cc=bp@suse.de \
--cc=james.morse@arm.com \
--cc=jamie@nuviainc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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