mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: linux-kernel@vger.kernel.org, Randy Dunlap <rdunlap@infradead.org>
Cc: Hans de Goede <hansg@kernel.org>,
	Vadim Pasternak <vadimp@nvidia.com>,
	 platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH] platform_data/mlxreg: mlxreg.h: fix all kernel-doc warnings
Date: Fri, 27 Feb 2026 13:38:36 +0200	[thread overview]
Message-ID: <177219231634.7567.8687956632443917408.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20260226051232.549537-1-rdunlap@infradead.org>

On Wed, 25 Feb 2026 21:12:29 -0800, Randy Dunlap wrote:

> Use the correct kernel-doc format & notation to eliminate
> kernel-doc warnings:
> 
> Warning: include/linux/platform_data/mlxreg.h:24 Enum value
>  'MLX_WDT_TYPE1' not described in enum 'mlxreg_wdt_type'
> Warning: include/linux/platform_data/mlxreg.h:24 Enum value
>  'MLX_WDT_TYPE2' not described in enum 'mlxreg_wdt_type'
> Warning: include/linux/platform_data/mlxreg.h:24 Enum value
>  'MLX_WDT_TYPE3' not described in enum 'mlxreg_wdt_type'
> Warning: include/linux/platform_data/mlxreg.h:37 bad line:
>  PHYs ready / unready state;
> Warning: include/linux/platform_data/mlxreg.h:153 struct member 'np'
>  not described in 'mlxreg_core_data'
> Warning: include/linux/platform_data/mlxreg.h:153 struct member 'hpdev'
>  not described in 'mlxreg_core_data'
> 
> [...]


Thank you for your contribution, it has been applied to my local
review-ilpo-fixes branch. Note it will show up in the public
platform-drivers-x86/review-ilpo-fixes branch only once I've pushed my
local branch there, which might take a while.

The list of commits applied:
[1/1] platform_data/mlxreg: mlxreg.h: fix all kernel-doc warnings
      commit: 3350c2b3f2b8a3b985a020a4ef4f2f050a4b6a1d

--
 i.


      reply	other threads:[~2026-02-27 11:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-26  5:12 Randy Dunlap
2026-02-27 11:38 ` Ilpo Järvinen [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=177219231634.7567.8687956632443917408.b4-ty@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=hansg@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=vadimp@nvidia.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

all inboxes | Powered by JetHome®