From: Ursula Braun <braunu@de.ibm.com>
To: jgarzik@pobox.com, netdev@vger.kernel.org, linux-s390@vger.kernel.org
Subject: [patch 1/5] claw: removal of volatile variables
Date: Fri, 08 Feb 2008 13:09:01 +0100 [thread overview]
Message-ID: <20080208121512.532071000@linux.vnet.ibm.com> (raw)
In-Reply-To: 20080208120900.295604000@linux.vnet.ibm.com
[-- Attachment #1: 719-claw-volatile.diff --]
[-- Type: text/plain, Size: 1013 bytes --]
From: Ursula Braun <braunu@de.ibm.com>
Volatile variables queme_switch and pk_delay are not used anyway.
They are just a left over from an unused timer based packing logic.
Signed-off-by: Ursula Braun <braunu@de.ibm.com>
---
drivers/s390/net/claw.h | 2 --
1 file changed, 2 deletions(-)
Index: linux-2.6-uschi/drivers/s390/net/claw.h
===================================================================
--- linux-2.6-uschi.orig/drivers/s390/net/claw.h
+++ linux-2.6-uschi/drivers/s390/net/claw.h
@@ -278,8 +278,6 @@ struct claw_env {
__u16 write_size; /* write buffer size */
__u16 dev_id; /* device ident */
__u8 packing; /* are we packing? */
- volatile __u8 queme_switch; /* gate for imed packing */
- volatile unsigned long pk_delay; /* Delay for adaptive packing */
__u8 in_use; /* device active flag */
struct net_device *ndev; /* backward ptr to the net dev*/
};
--
next prev parent reply other threads:[~2008-02-08 12:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 12:09 [patch 0/5] s390: claw/lcs/netiucv network driver patches for 2.6.25 Ursula Braun
2008-02-08 12:09 ` Ursula Braun [this message]
2008-02-11 16:15 ` [patch 1/5] claw: removal of volatile variables Jeff Garzik
2008-02-08 12:09 ` [patch 2/5] netiucv: Remember to set driver->owner Ursula Braun
2008-02-08 12:09 ` [patch 3/5] netiucv: change name of nop function Ursula Braun
2008-02-08 12:09 ` [patch 4/5] lcs: avoid/reduce unused s390dbf debug areas Ursula Braun
2008-02-08 12:09 ` [patch 5/5] claw/lcs/netiucv: check s390dbf level before sprints Ursula Braun
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=20080208121512.532071000@linux.vnet.ibm.com \
--to=braunu@de.ibm.com \
--cc=jgarzik@pobox.com \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.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).