From: Ian Abbott <abbotti@mev.co.uk>
To: Hartley Sweeten <HartleyS@visionengravers.com>,
"Pablo G. Gallardo" <gallardo_pablo@hotmail.com>,
"greg@kroah.com" <greg@kroah.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] STAGING: COMEDI: Wrap line over 80 characters
Date: Mon, 1 Feb 2016 16:50:18 +0000 [thread overview]
Message-ID: <56AF8CCA.30303@mev.co.uk> (raw)
In-Reply-To: <BN3PR0101MB105772C9F071E3A9E9BFC7A0D0DE0@BN3PR0101MB1057.prod.exchangelabs.com>
On 01/02/16 16:35, Hartley Sweeten wrote:
> On Monday, February 01, 2016 5:26 AM, Ian Abbott wrote:
>> On 01/02/16 01:06, Pablo G. Gallardo wrote:
>>> This patch wraps lines over 80 characters.
>>>
>>> Signed-off-by: Pablo G. Gallardo <gallardo_pablo@hotmail.com>
>>> ---
>>> drivers/staging/comedi/comedi_pcmcia.h | 3 ++-
>>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/staging/comedi/comedi_pcmcia.h b/drivers/staging/comedi/comedi_pcmcia.h
>>> index 5d3db2b..5a572c2 100644
>>> --- a/drivers/staging/comedi/comedi_pcmcia.h
>>> +++ b/drivers/staging/comedi/comedi_pcmcia.h
>>> @@ -39,7 +39,8 @@ void comedi_pcmcia_driver_unregister(struct comedi_driver *,
>>> struct pcmcia_driver *);
>>>
>>> /**
>>> - * module_comedi_pcmcia_driver() - Helper macro for registering a comedi PCMCIA driver
>>> + * module_comedi_pcmcia_driver() - Helper macro for registering a comedi
>>> + * PCMCIA driver
>>> * @__comedi_driver: comedi_driver struct
>>> * @__pcmcia_driver: pcmcia_driver struct
>>> *
>
> Doesn't this break the docbook format?
It doesn't break the kernel-doc format: "The short description following
the subject can span multiple lines and ends with an @argument
description, an empty line or the end of the comment block."
Some people prefer it on a single line, some people indent the
continuation line(s), and some people do it without indentation as above.
--
-=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=-
-=( Web: http://www.mev.co.uk/ )=-
prev parent reply other threads:[~2016-02-01 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1454288761-1329-1-git-send-email-gallardo_pablo@hotmail.com>
[not found] ` <BLU437-SMTP329AD431F8560BE4FC2CC7FEDE0@phx.gbl>
2016-02-01 12:26 ` [PATCH 2/2] STAGING: COMEDI: Wrap line over 80 characters Ian Abbott
2016-02-01 16:35 ` Hartley Sweeten
2016-02-01 16:50 ` Ian Abbott [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=56AF8CCA.30303@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=HartleyS@visionengravers.com \
--cc=gallardo_pablo@hotmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.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