From: David Miller <davem@davemloft.net>
To: rdunlap@xenotime.net
Cc: shemminger@linux-foundation.org, netdev@vger.kernel.org
Subject: Re: [PATCH] net: docbook fixes for netif_ functions
Date: Thu, 01 Nov 2007 02:22:09 -0700 (PDT) [thread overview]
Message-ID: <20071101.022209.141061101.davem@davemloft.net> (raw)
In-Reply-To: <20071031153620.01cf5eeb.rdunlap@xenotime.net>
From: Randy Dunlap <rdunlap@xenotime.net>
Date: Wed, 31 Oct 2007 15:36:20 -0700
> > + * return values (usually ignored).
> > + * NET_RX_SUCCESS (no congestion)
> > + * NET_RX_DROP (packet was dropped)
>
> For the 3 lines above, how about:
>
> * Return values (usually ignored):
> * NET_RX_SUCCESS: no congestion
> * NET_RX_DROP: packet was dropped
>
>
> only because they come out of kernel-doc badly, munged together like so:
>
> return values (usually ignored). NET_RX_SUCCESS (no congestion)
> NET_RX_DROP (packet was dropped)
I've applied Stephen's patch with this minor correction
added.
prev parent reply other threads:[~2007-11-01 9:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-31 21:08 [PATCH] net: docbook fixes for netif_ functions Stephen Hemminger
2007-10-31 22:36 ` Randy Dunlap
2007-11-01 9:22 ` David Miller [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=20071101.022209.141061101.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=shemminger@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