From: Randy Dunlap <rdunlap@infradead.org>
To: "Winiarska, Iwona" <iwona.winiarska@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: [PATCH] peci: linux/peci.h: fix Excess kernel-doc description warning
Date: Wed, 27 Mar 2024 21:47:49 -0700 [thread overview]
Message-ID: <d9bf12c1-4d21-40d4-9abe-95a4d8b59d8f@infradead.org> (raw)
In-Reply-To: <a3ea93b54911f553a6ca37d33181be0cf9f89b07.camel@intel.com>
On 1/10/24 06:19, Winiarska, Iwona wrote:
> On Fri, 2023-12-22 at 21:06 -0800, Randy Dunlap wrote:
>> Remove the @controller: line to prevent the kernel-doc warning:
>>
>> include/linux/peci.h:84: warning: Excess struct member 'controller'
>> description in 'peci_device'
>>
>> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
>> Cc: Iwona Winiarska <iwona.winiarska@intel.com>
>> Cc: openbmc@lists.ozlabs.org
>
> Reviewed-by: Iwona Winiarska <iwona.winiarska@intel.com>
>
> Thanks
> -Iwona
Hi Iwona,
Who should be merging this patch?
Thanks.
>
>> ---
>> include/linux/peci.h | 1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff -- a/include/linux/peci.h b/include/linux/peci.h
>> --- a/include/linux/peci.h
>> +++ b/include/linux/peci.h
>> @@ -58,7 +58,6 @@ static inline struct peci_controller *to
>> /**
>> * struct peci_device - PECI device
>> * @dev: device object to register PECI device to the device model
>> - * @controller: manages the bus segment hosting this PECI device
>> * @info: PECI device characteristics
>> * @info.family: device family
>> * @info.model: device model
>
--
#Randy
prev parent reply other threads:[~2024-03-28 4:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-23 5:06 [PATCH] peci: linux/peci.h: fix Excess kernel-doc description warning Randy Dunlap
2024-01-10 14:19 ` Winiarska, Iwona
2024-03-28 4:47 ` Randy Dunlap [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=d9bf12c1-4d21-40d4-9abe-95a4d8b59d8f@infradead.org \
--to=rdunlap@infradead.org \
--cc=iwona.winiarska@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).