From: Jani Nikula <jani.nikula@intel.com>
To: abid-sayyad <sayyad.abid16@gmail.com>, airlied@gmail.com
Cc: daniel@ffwll.ch, dmitry.baryshkov@linaro.org, mripard@kernel.org,
ankit.k.nautiyal@intel.com, imre.deak@intel.com,
mitulkumar.ajitkumar.golani@intel.com, quic_abhinavk@quicinc.com,
dianders@chromium.org, marilene.agarcia@gmail.com,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
tytso@mit.edu, jack@suse.com, linux-ext4@vger.kernel.org,
skhan@linuxfoundation.org, abid-sayyad <sayyad.abid16@gmail.com>
Subject: Re: [PATCH] fix member variable description warnings while building docs
Date: Mon, 19 Aug 2024 10:34:09 +0300 [thread overview]
Message-ID: <87a5h96k5q.fsf@intel.com> (raw)
In-Reply-To: <20240818112543.1089986-1-sayyad.abid16@gmail.com>
On Sun, 18 Aug 2024, abid-sayyad <sayyad.abid16@gmail.com> wrote:
> Fix the following warnings while building the docs :-
>
> ./include/linux/jbd2.h:1303: warning: Function parameter or struct member
> 'j_transaction_overhead_buffers' not described in 'journal_s'
> ./include/linux/jbd2.h:1303: warning: Excess struct member
> 'j_transaction_overhead' description in 'journal_s'
>
> Fix spelling error for j_transaction_overhead to j_transaction_overhead_buffers.
>
> ./include/drm/display/drm_dp_helper.h:127: warning: Function parameter or struct
> member 'target_rr_divider' not described in 'drm_dp_as_sdp'
>
> Add description for the 'target_rr_divider' member.
Please send the two separately. They are part of two completely
different subsystems.
BR,
Jani.
>
> Signed-off-by: abid-sayyad <sayyad.abid16@gmail.com>
> ---
> include/drm/display/drm_dp_helper.h | 1 +
> include/linux/jbd2.h | 2 +-
> 2 files changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/include/drm/display/drm_dp_helper.h b/include/drm/display/drm_dp_helper.h
> index ea03e1dd26ba..7f2567fa230d 100644
> --- a/include/drm/display/drm_dp_helper.h
> +++ b/include/drm/display/drm_dp_helper.h
> @@ -112,6 +112,7 @@ struct drm_dp_vsc_sdp {
> * @target_rr: Target Refresh
> * @duration_incr_ms: Successive frame duration increase
> * @duration_decr_ms: Successive frame duration decrease
> + * @target_rr_divider: Target refresh rate divider
> * @mode: Adaptive Sync Operation Mode
> */
> struct drm_dp_as_sdp {
> diff --git a/include/linux/jbd2.h b/include/linux/jbd2.h
> index 5157d92b6f23..17662eae408f 100644
> --- a/include/linux/jbd2.h
> +++ b/include/linux/jbd2.h
> @@ -1086,7 +1086,7 @@ struct journal_s
> int j_revoke_records_per_block;
>
> /**
> - * @j_transaction_overhead:
> + * @j_transaction_overhead_buffers:
> *
> * Number of blocks each transaction needs for its own bookkeeping
> */
> --
> 2.39.2
>
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-08-19 7:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-18 11:25 [PATCH] fix member variable description warnings while building docs abid-sayyad
2024-08-19 7:34 ` Jani Nikula [this message]
2024-08-19 7:51 ` Golani, Mitulkumar Ajitkumar
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=87a5h96k5q.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=airlied@gmail.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=daniel@ffwll.ch \
--cc=dianders@chromium.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=imre.deak@intel.com \
--cc=jack@suse.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marilene.agarcia@gmail.com \
--cc=mitulkumar.ajitkumar.golani@intel.com \
--cc=mripard@kernel.org \
--cc=quic_abhinavk@quicinc.com \
--cc=sayyad.abid16@gmail.com \
--cc=skhan@linuxfoundation.org \
--cc=tytso@mit.edu \
/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