From: "Randy.Dunlap" <rddunlap@osdl.org>
To: <davem@redhat.com>
Cc: <netdev@oss.sgi.com>, <linux-net@vger.kernel.org>
Subject: remove unused kernel_stat fields
Date: Tue, 9 Apr 2002 14:02:30 -0700 (PDT) [thread overview]
Message-ID: <a8vp5i$c62$2@main.gmane.org> (raw)
Dave, anyone-
I can't find any references to these fields in struct kernel_stat.
Can they be removed...or is there non-kernel code that needs to
have them in the kernel?
Patch against 2.5.8-pre2. Please apply.
--- linux-258-pre2/include/linux/kernel_stat.h.STAT Tue Apr 9 12:43:14 2002
+++ linux-258-pre2/include/linux/kernel_stat.h Tue Apr 9 13:40:51 2002
@@ -29,9 +29,6 @@
#if !defined(CONFIG_ARCH_S390)
unsigned int irqs[NR_CPUS][NR_IRQS];
#endif
- unsigned int ipackets, opackets;
- unsigned int ierrors, oerrors;
- unsigned int collisions;
};
extern struct kernel_stat kstat;
--
~Randy
next reply other threads:[~2002-04-09 21:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-09 21:02 Randy.Dunlap [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-09 21:02 remove unused kernel_stat fields Randy.Dunlap
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='a8vp5i$c62$2@main.gmane.org' \
--to=rddunlap@osdl.org \
--cc=davem@redhat.com \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.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).