From: Ron Mercer <ron.mercer@qlogic.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, ron.mercer@qlogic.com, linux-driver@qlogic.com
Subject: [PATCH 0/5] qlge: Warning fixes and cleanup.
Date: Fri, 9 Jan 2009 13:30:45 -0800 [thread overview]
Message-ID: <20090109213045.GD10803@susedev.qlogic.org> (raw)
Dave,
This series includes the change from volatile to rmb() usage that you
asked for from the last set of patches. I've also included a warning
fix and some clean up.
Regards,
Ron Mercer
next reply other threads:[~2009-01-09 21:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 21:30 Ron Mercer [this message]
2009-01-09 21:31 ` [PATCH 1/5] qlge: Get rid of volatile usage for shadow register Ron Mercer
2009-01-10 7:11 ` David Miller
2009-01-09 21:31 ` [PATCH 2/5] qlge: Get rid of split addresses in hardware control blocks Ron Mercer
2009-01-10 7:11 ` David Miller
2009-01-09 21:31 ` [PATCH 3/5] qlge: Remove support for device ID 8000 Ron Mercer
2009-01-10 7:11 ` David Miller
2009-01-09 21:31 ` [PATCH 4/5] qlge: Fix schedule while atomic issue Ron Mercer
2009-01-10 7:11 ` David Miller
2009-01-09 21:31 ` [PATCH 5/5] qlge: Remove dynamic alloc of rx ring control blocks Ron Mercer
2009-01-10 7:11 ` David Miller
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=20090109213045.GD10803@susedev.qlogic.org \
--to=ron.mercer@qlogic.com \
--cc=davem@davemloft.net \
--cc=linux-driver@qlogic.com \
--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).