All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bhelgaas@google.com>
To: Yijing Wang <wangyijing@huawei.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI: Trivial comment fix
Date: Thu, 18 Jun 2015 11:24:54 -0500	[thread overview]
Message-ID: <20150618162454.GC7710@google.com> (raw)
In-Reply-To: <1434628020-4143-1-git-send-email-wangyijing@huawei.com>

Hi Yijing,

The subject should start with a verb, e.g., "Fix DocBook comments".

On Thu, Jun 18, 2015 at 07:47:00PM +0800, Yijing Wang wrote:

This needs a changelog, even if it's a trivial one.

> Signed-off-by: Yijing Wang <wangyijing@huawei.com>
> ---
>  drivers/pci/hotplug/pci_hotplug_core.c |    6 +++---
>  1 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/pci/hotplug/pci_hotplug_core.c b/drivers/pci/hotplug/pci_hotplug_core.c
> index 56d8486..117c8f9 100644
> --- a/drivers/pci/hotplug/pci_hotplug_core.c
> +++ b/drivers/pci/hotplug/pci_hotplug_core.c
> @@ -408,8 +408,8 @@ static struct hotplug_slot *get_slot_from_name(const char *name)
>  
>  /**
>   * __pci_hp_register - register a hotplug_slot with the PCI hotplug subsystem
> - * @bus: bus this slot is on
>   * @slot: pointer to the &struct hotplug_slot to register
> + * @bus: bus this slot is on
>   * @devnr: device number
>   * @name: name registered with kobject core
>   * @owner: caller module owner
> @@ -469,7 +469,7 @@ EXPORT_SYMBOL_GPL(__pci_hp_register);
>   * pci_hp_deregister - deregister a hotplug_slot with the PCI hotplug subsystem
>   * @hotplug: pointer to the &struct hotplug_slot to deregister
>   *
> - * The @slot must have been registered with the pci hotplug subsystem
> + * The @hotplug must have been registered with the pci hotplug subsystem

This doesn't read like English because "hotplug" is not a noun.

Please extend your patch so the entire file consistently uses "slot" for a
struct hotplug_slot, and "pci_slot" for a struct pci_slot.  Right now, the
file is a mix of random names, which is confusing and leads to errors.

You might need to do this with more than one patch to make it possible to
review it.

>   * previously with a call to pci_hp_register().
>   *
>   * Returns 0 if successful, anything else for an error.
> @@ -509,7 +509,7 @@ EXPORT_SYMBOL_GPL(pci_hp_deregister);
>   * @hotplug: pointer to the slot whose info has changed
>   * @info: pointer to the info copy into the slot's info structure
>   *
> - * @slot must have been registered with the pci
> + * @hotplug must have been registered with the pci
>   * hotplug subsystem previously with a call to pci_hp_register().
>   *
>   * Returns 0 if successful, anything else for an error.
> -- 
> 1.7.1
> 

  reply	other threads:[~2015-06-18 16:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-18 11:47 [PATCH] PCI: Trivial comment fix Yijing Wang
2015-06-18 16:24 ` Bjorn Helgaas [this message]
2015-06-19  3:36   ` Yijing Wang

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=20150618162454.GC7710@google.com \
    --to=bhelgaas@google.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=wangyijing@huawei.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 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.