From: Stephen Hemminger <shemminger@osdl.org>
To: "Amit S. Kale" <amitkale@linsyssoft.com>
Cc: "Amit S. Kale" <amitkale@netxen.com>,
netdev@vger.kernel.org, jeff@garzik.org, sanjeev@netxen.com,
unmproj@linsyssoft.com, rob@netxen.com
Subject: Re: [PATCH 2.6.17 2/9] NetXen: Hardware access routines
Date: Mon, 21 Aug 2006 07:03:02 -0700 [thread overview]
Message-ID: <20060821070302.5666e1ab@localhost.localdomain> (raw)
In-Reply-To: <200608211357.23600.amitkale@linsyssoft.com>
On Mon, 21 Aug 2006 13:57:23 +0530
"Amit S. Kale" <amitkale@linsyssoft.com> wrote:
> We can certainly create a table for all error messages. It'll hurt readability
> of code in many of the other places where printks are used to indicate some
> hardware error.
> -Amit
My suggestion was intended as an way to handle multiple driver versions
all using the same firmware or vice versa. By locking the firmware and
driver version together you might make maintenance more difficult.
next prev parent reply other threads:[~2006-08-21 14:03 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 14:38 [PATCH 2.6.17 0/9] NetXen: 1G/10G Ethernet Driver Amit S. Kale
2006-08-18 14:44 ` [PATCH 2.6.17 1/9] NetXen: Makefile and driver main file Amit S. Kale
2006-08-18 14:58 ` [PATCH 2.6.17 2/9] NetXen: Hardware access routines Amit S. Kale
2006-08-18 15:16 ` Stephen Hemminger
2006-08-21 8:27 ` Amit S. Kale
2006-08-21 14:03 ` Stephen Hemminger [this message]
2006-08-25 18:23 ` Sanjeev Jorapur
2006-08-28 9:52 ` Amit S. Kale
2006-08-21 9:55 ` [PATCH 2.6.17 2/9] NetXen: Hardware access routines (name prefixed) Pradeep Dalvi
2006-08-21 10:01 ` [PATCH 2.6.17 1/9] NetXen: Makefile and driver main file (name prefix change) Pradeep Dalvi
2006-08-18 15:01 ` [PATCH 2.6.17 3/9] NetXen: hw initialization routines Amit S. Kale
2006-08-21 10:04 ` [PATCH 2.6.17 3/9] NetXen: hw initialization routines (name prefix change) Pradeep Dalvi
2006-08-18 15:04 ` [PATCH 2.6.17 4/9] NetXen: intr routines and niu handling Amit S. Kale
2006-08-18 15:22 ` Stephen Hemminger
2006-08-21 8:40 ` Amit S. Kale
2006-08-18 15:06 ` [PATCH 2.6.17 5/9] NetXen: ethtool interface Amit S. Kale
2006-08-18 15:10 ` [PATCH 2.6.17 6/9] NetXen: Main header file Amit S. Kale
2006-08-21 10:05 ` [PATCH 2.6.17 6/9] NetXen: Main header file (Name prefix change) Pradeep Dalvi
2006-08-18 15:12 ` [PATCH 2.6.17 7/9] NetXen: hw access routines header file Amit S. Kale
2006-08-18 15:14 ` [PATCH 2.6.17 8/9] NetXen: Header file and ioctl " Amit S. Kale
2006-08-18 15:17 ` [PATCH 2.6.17 9/9] NetXen: CRB reg defininitions Amit S. Kale
2006-08-22 7:43 ` [PATCH 2.6.17 0/9] NetXen: 1G/10G Ethernet Driver Pradeep Dalvi
2006-08-24 0:04 ` Don Fry
2006-08-25 13:19 ` Amit S. Kale
2006-08-24 20:36 ` [PATCH 2.6.17 0/9] NetXen: 1G/10G Ethernet Driver - patch for big-endian systems wen xiong
2006-08-24 21:29 ` Michael Buesch
2006-08-24 21:40 ` Francois Romieu
2006-08-25 13:18 ` Amit S. Kale
-- strict thread matches above, loose matches on Subject: below --
2006-08-31 14:02 [PATCH 2.6.17 0/9] NetXen: 1G/10G Ethernet Driver Amit S. Kale
2006-08-31 14:13 ` [PATCH 2.6.17 2/9] NetXen: Hardware access routines Amit S. Kale
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=20060821070302.5666e1ab@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=amitkale@linsyssoft.com \
--cc=amitkale@netxen.com \
--cc=jeff@garzik.org \
--cc=netdev@vger.kernel.org \
--cc=rob@netxen.com \
--cc=sanjeev@netxen.com \
--cc=unmproj@linsyssoft.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).