All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: Sudeep Holla <sudeep.holla@arm.com>,
	linux-arm-kernel@lists.infradead.org
Cc: Cristian Marussi <cristian.marussi@arm.com>
Subject: Re: [PATCH] firmware: arm_scmi: Fix kernel doc warnings
Date: Wed, 14 Jul 2021 17:39:48 +0100	[thread overview]
Message-ID: <162628075100.2616138.4444659383388540389.b4-ty@arm.com> (raw)
In-Reply-To: <20210712130801.2436492-2-sudeep.holla@arm.com>

On Mon, 12 Jul 2021 14:08:01 +0100, Sudeep Holla wrote:
> Kernel doc validation script is unhappy and complains with the below set
> of warnings.
> 
>  | Function parameter or member 'fast_switch_possible' not described in 'scmi_perf_proto_ops'
>  | Function parameter or member 'power_scale_mw_get' not described in 'scmi_perf_proto_ops'
>  | cannot understand function prototype: 'struct scmi_sensor_reading '
>  | cannot understand function prototype: 'struct scmi_range_attrs '
>  | cannot understand function prototype: 'struct scmi_sensor_axis_info '
>  | cannot understand function prototype: 'struct scmi_sensor_intervals_info '
> 
> [...]

Applied to sudeep.holla/linux (for-next/scmi), thanks!

[1/1] firmware: arm_scmi: Fix kernel doc warnings
      https://git.kernel.org/sudeep.holla/c/52f83955aa

--
Regards,
Sudeep


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      parent reply	other threads:[~2021-07-14 16:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-12 13:08 [PATCH] firmware: arm_scpi: Fix kernel doc warnings Sudeep Holla
2021-07-12 13:08 ` [PATCH] firmware: arm_scmi: " Sudeep Holla
2021-07-12 14:32   ` Cristian Marussi
2021-07-14 16:39   ` Sudeep Holla [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=162628075100.2616138.4444659383388540389.b4-ty@arm.com \
    --to=sudeep.holla@arm.com \
    --cc=cristian.marussi@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.