From: Ursula Braun <braunu@de.ibm.com>
To: jgarzik@pobox.com, netdev@vger.kernel.org, linux-s390@vger.kernel.org
Subject: [patch 0/5] s390: claw/lcs/netiucv network driver patches for 2.6.25
Date: Fri, 08 Feb 2008 13:09:00 +0100 [thread overview]
Message-ID: <20080208120900.295604000@linux.vnet.ibm.com> (raw)
--
Jeff,
The following patches are intended for 2.6.25.
They affect the s390 network drivers claw, lcs, and netiucv.
Patch summary:
claw: remove unused volatile variables
netiucv: define module owner in device_driver structure
netiucv: renaming of NOP action
lcs: improvement for debug area setup
claw/lcs/netiucv: optimize a debugging macro
Regards, Ursula Braun
next 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 Ursula Braun [this message]
2008-02-08 12:09 ` [patch 1/5] claw: removal of volatile variables Ursula Braun
2008-02-11 16:15 ` 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=20080208120900.295604000@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).