From: David Miller <davem@davemloft.net>
To: rdunlap@xenotime.net
Cc: shemminger@vyatta.com, netdev@vger.kernel.org
Subject: Re: [PATCH 2/2] netdev: docbook comment update (revised)
Date: Tue, 30 Sep 2008 02:24:41 -0700 (PDT) [thread overview]
Message-ID: <20080930.022441.32388035.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0809231010280.27041@shark.he.net>
From: "Randy.Dunlap" <rdunlap@xenotime.net>
Date: Tue, 23 Sep 2008 10:12:04 -0700 (PDT)
> On Tue, 23 Sep 2008, Stephen Hemminger wrote:
>
> > +/**
> > + * dev_get_flags - get flags reported to userspace
> > + * @dev: device
> > + *
> > + * Get the combination of flag bits exported throug APIs to userspace.
>
>
> still needs: through
I've applied Stephen's patch with this fix.
prev parent reply other threads:[~2008-09-30 9:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080923083750.59eaac97@extreme>
[not found] ` <20080923091035.102d4106@extreme>
2008-09-23 16:19 ` [PATCH 2/2] netdev: docbook comment update Randy.Dunlap
2008-09-23 17:02 ` [PATCH 2/2] netdev: docbook comment update (revised) Stephen Hemminger
2008-09-23 17:12 ` Randy.Dunlap
2008-09-30 9:24 ` 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=20080930.022441.32388035.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=shemminger@vyatta.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;
as well as URLs for NNTP newsgroup(s).