From: "Jeff Kirsher" <jeffrey.t.kirsher@intel.com>
To: "Qinghuang Feng" <qhfeng.kernel@gmail.com>
Cc: "David Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] driver/net/*: remove redundant argument comments
Date: Fri, 21 Nov 2008 23:55:27 -0800 [thread overview]
Message-ID: <9929d2390811212355j635e0e8iee0e53678efc5f09@mail.gmail.com> (raw)
In-Reply-To: <4927b790.0e0d6e0a.65cc.ffffcb05@mx.google.com>
On Fri, Nov 21, 2008 at 11:40 PM, Qinghuang Feng
<qhfeng.kernel@gmail.com> wrote:
> remove redundant argument comments in files of drivers/net/*
>
> Signed-off-by: Qinghuang Feng <qhfeng.kernel@gmail.com>
> ---
> diff --git a/drivers/net/e1000e/netdev.c b/drivers/net/e1000e/netdev.c
> index 91795f7..122539a 100644
> --- a/drivers/net/e1000e/netdev.c
> +++ b/drivers/net/e1000e/netdev.c
> @@ -345,7 +345,6 @@ no_buffers:
> /**
> * e1000_alloc_jumbo_rx_buffers - Replace used jumbo receive buffers
> * @adapter: address of board private structure
> - * @rx_ring: pointer to receive ring structure
> * @cleaned_count: number of buffers to allocate this pass
> **/
>
NAK - rather than removing documentation, I would suggest improving
the documentation. Your suggested patch removes lines in the function
headers which can be (if not already) in documentation. Specifically,
the function header comments for Intel drivers was written in such a
way that it can be parsed out by the kernel documentation scripts to
create an API document.
I would agree that "@rx_ring: pointer to receive ring structure" is
probably not the best documentation, but rather than removing it, I
would suggest improving it.
--
Cheers,
Jeff
next prev parent reply other threads:[~2008-11-22 7:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-22 7:40 Qinghuang Feng
2008-11-22 7:55 ` Jeff Kirsher [this message]
2008-11-22 7:56 ` David Miller
2008-11-22 8:10 ` Jeff Kirsher
2008-11-22 11:40 ` Alan Cox
2008-11-23 23:47 ` David Miller
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=9929d2390811212355j635e0e8iee0e53678efc5f09@mail.gmail.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=qhfeng.kernel@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®