From: Michael Ellerman <michael@ellerman.id.au>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
torvalds <torvalds@linux-foundation.org>,
jbarnes@virtuousgeek.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH] pci kernel-doc fatal error
Date: Tue, 22 Jul 2008 09:07:45 +1000 [thread overview]
Message-ID: <1216681665.7427.9.camel@localhost> (raw)
In-Reply-To: <20080721092718.f15dc1ea.randy.dunlap@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 2003 bytes --]
On Mon, 2008-07-21 at 09:27 -0700, Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
>
> Fix kernel-doc comments so that they don't produce errors.
> Also cut some extraneous copy-paste text.
>
> Error(linhead//drivers/pci/pci.c:1133): duplicate section name 'Description'
> Error(linhead//drivers/pci/pci.c:1189): duplicate section name 'Description'
But now the description lines exceed 80 columns, and with longer
function names it's even harder to write a meaningful description in
under 80 columns.
Couldn't kerneldoc be modified to accept multiline descriptions? I know
they're /short/ descriptions, but still.
cheers
ps. I did look at changing kerneldoc to do that myself, but whereas
previously I thought I didn't really know perl, now I /know/ I totally
don't know perl ;)
> --- linhead.orig/drivers/pci/pci.c
> +++ linhead/drivers/pci/pci.c
> @@ -1123,8 +1123,7 @@ int pci_enable_wake(struct pci_dev *dev,
> }
>
> /**
> - * pci_prepare_to_sleep - prepare PCI device for system-wide transition into
> - * a sleep state
> + * pci_prepare_to_sleep - prepare PCI device for system-wide transition into a sleep state
> * @dev: Device to handle.
> *
> * Choose the power state appropriate for the device depending on whether
> @@ -1181,8 +1180,7 @@ int pci_prepare_to_sleep(struct pci_dev
> }
>
> /**
> - * pci_back_from_sleep - turn PCI device on during system-wide transition into
> - * the working state a sleep state
> + * pci_back_from_sleep - turn PCI device on during system-wide transition into working state
> * @dev: Device to handle.
> *
> * Disable device's sytem wake-up capability and put it into D0.
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-07-21 23:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 16:27 [PATCH] pci kernel-doc fatal error Randy Dunlap
2008-07-21 23:07 ` Michael Ellerman [this message]
2008-07-21 23:14 ` Randy Dunlap
2008-07-22 2:29 ` Michael Ellerman
2008-07-22 4:51 ` Randy Dunlap
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=1216681665.7427.9.camel@localhost \
--to=michael@ellerman.id.au \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--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 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.