linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bhelgaas@google.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-pci <linux-pci@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] pci: fix kernel-doc notation warning
Date: Tue, 11 Feb 2014 17:43:14 -0700	[thread overview]
Message-ID: <20140212004314.GG21057@google.com> (raw)
In-Reply-To: <52EF06C0.1050104@infradead.org>

On Sun, Feb 02, 2014 at 07:02:24PM -0800, Randy Dunlap wrote:
> From: Randy Dunlap <rdunlap@infradead.org>
> 
> Fix a "blank" kernel-doc line to have an asterisk instead of
> being totally empty.  This fixes the kernel-doc warning:
> 
> Warning(drivers/pci/msi.c:962): bad line: 
> 
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>

I applied this fix already (but it's not in -next yet):

http://git.kernel.org/cgit/linux/kernel/git/helgaas/pci.git/commit/?h=pci/msi&id=39af663b5fd25c9dd427e12e106763b6b4f9572c

Thanks!

Bjorn

> ---
>  drivers/pci/msi.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> --- lnx-314-rc1.orig/drivers/pci/msi.c
> +++ lnx-314-rc1/drivers/pci/msi.c
> @@ -959,7 +959,7 @@ EXPORT_SYMBOL(pci_disable_msi);
>  /**
>   * pci_msix_vec_count - return the number of device's MSI-X table entries
>   * @dev: pointer to the pci_dev data structure of MSI-X device function
> -
> + *
>   * This function returns the number of device's MSI-X table entries and
>   * therefore the number of MSI-X vectors device is capable of sending.
>   * It returns a negative errno if the device is not capable of sending MSI-X

      reply	other threads:[~2014-02-12  0:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-03  3:02 [PATCH] pci: fix kernel-doc notation warning Randy Dunlap
2014-02-12  0:43 ` Bjorn Helgaas [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=20140212004314.GG21057@google.com \
    --to=bhelgaas@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).