From: "David S. Miller" <davem@redhat.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: levon@movementarian.org, netdev@oss.sgi.com
Subject: Re: [PATCH] proc_net macro's for non-proc-fs case
Date: Fri, 12 Sep 2003 17:13:41 -0700 [thread overview]
Message-ID: <20030912171341.60157cbc.davem@redhat.com> (raw)
In-Reply-To: <20030912112120.23300a99.shemminger@osdl.org>
On Fri, 12 Sep 2003 11:21:20 -0700
Stephen Hemminger <shemminger@osdl.org> wrote:
> The following should work better. They have the desired properties that:
> - return value makes sense for those that might check
> - arguments fops and info don't have to be defined (ie can be #ifdef'd out)
> - generate no warnings for null effect.
Looks good, applied thanks.
prev parent reply other threads:[~2003-09-13 0:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-11 22:43 [PATCH] ipv4 -- proc_net_fops_create Stephen Hemminger
2003-09-11 22:50 ` YOSHIFUJI Hideaki / 吉藤英明
2003-09-11 23:03 ` David S. Miller
[not found] ` <20030911235405.GA74116@compsoc.man.ac.uk>
2003-09-12 18:21 ` [PATCH] proc_net macro's for non-proc-fs case Stephen Hemminger
2003-09-13 0:13 ` David S. 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=20030912171341.60157cbc.davem@redhat.com \
--to=davem@redhat.com \
--cc=levon@movementarian.org \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.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;
as well as URLs for NNTP newsgroup(s).