Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Krzysztof Wilczy??ski <kw@linux.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	Scott Murray <scott@spiteful.org>,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH v3] PCI: hotplug: Fix kernel-doc formatting and add missing documentation
Date: Sat, 3 Jul 2021 08:48:48 +0200	[thread overview]
Message-ID: <20210703064848.GA24279@wunner.de> (raw)
In-Reply-To: <20210702231541.1671875-1-kw@linux.com>

On Fri, Jul 02, 2021 at 11:15:41PM +0000, Krzysztof Wilczy??ski wrote:
> Fix kernel-doc formatting and add missing documentation for the
[...]
>   drivers/pci/hotplug/pciehp.h:110: warning: Function parameter or member 'inband_presence_disabled' not described in 'controller'
[...]
> diff --git a/drivers/pci/hotplug/pciehp.h b/drivers/pci/hotplug/pciehp.h
> index 4fd200d8b0a9..c8b2b1e046e8 100644
> --- a/drivers/pci/hotplug/pciehp.h
> +++ b/drivers/pci/hotplug/pciehp.h
> @@ -44,38 +44,54 @@ extern int pciehp_poll_time;
>  #define SLOT_NAME_SIZE 10
>  
>  /**
> - * struct controller - PCIe hotplug controller
> - * @pcie: pointer to the controller's PCIe port service device
> - * @slot_cap: cached copy of the Slot Capabilities register
> - * @slot_ctrl: cached copy of the Slot Control register
[...]
> + * struct controller - PCIe hotplug controller.
> + * @pcie:			Pointer to the controller's PCIe port service
> + *				device.
> + * @slot_cap:			Cached copy of the Slot Capabilities register.

Is it really necessary to change the indentation and add the trailing
period *everywhere*?  What value does that add?

Changes like this make it more difficult to determine the commit from
which a certain line originates.

I respectfully submit that the formatting is fine and there's nothing
to be "fixed" here (as the commit message claims).


> + * @inband_presence_disabled:	Flag to used to track whether the in-band
> + *				presence detection is disabled.

That's not proper English and also not very useful because the documentation
merely repeats what the flag's name says.  I'd suggest something along the
lines of:

 * @inband_presence_disabled: whether In-Band Presence Detect Disable is
 *	supported by the controller and disabled per spec recommendation
 *	(PCIe r5.0, appendix I implementation note)

Thanks,

Lukas

  reply	other threads:[~2021-07-03  6:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-02 23:15 [PATCH v3] PCI: hotplug: Fix kernel-doc formatting and add missing documentation Krzysztof Wilczyński
2021-07-03  6:48 ` Lukas Wunner [this message]
2021-07-03  8:51   ` Krzysztof Wilczy??ski

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=20210703064848.GA24279@wunner.de \
    --to=lukas@wunner.de \
    --cc=bhelgaas@google.com \
    --cc=kw@linux.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=scott@spiteful.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