From: David Miller <davem@davemloft.net>
To: Shyam_Iyer@Dell.com
Cc: akpm@linux-foundation.org, kxie@chelsio.com,
netdev@vger.kernel.org, open-iscsi@googlegroups.com,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
jgarzik@pobox.com, michaelc@cs.wisc.edu,
swise@opengridcomputing.com, rdreier@cisco.com,
daisyc@us.ibm.com, wenxiong@us.ibm.com, bhua@us.ibm.com,
divy@chelsio.com, dm@chelsio.com, leedom@chelsio.com
Subject: Re: [PATCH 4/4 2.6.28] cxgb3i - cxgb3i iscsi driver
Date: Sat, 23 Aug 2008 02:29:34 -0700 (PDT) [thread overview]
Message-ID: <20080823.022934.127206564.davem@davemloft.net> (raw)
In-Reply-To: <46A00B48CC54E4468EF6911F877AC4CA018D73BC@blrx3m10.blr.amer.dell.com>
From: <Shyam_Iyer@Dell.com>
Date: Sat, 23 Aug 2008 14:37:53 +0530
> Exactly. And I am also suggesting that the driver version is not
> standard among different vendors.
It should not be standardized because every driver maintainer works
differently, and every driver is developed differently, and therefore
has different needs and desires for the version number.
All that matters is that the driver version makes sense to the
person maintaining the driver, and works for them when reviewing
bug reports.
Look, what you're suggesting is to change existing practice and that
doesn't belong in the discussion of the review of a specific driver.
If you want to bring that up as a topic and change globally how that
is handled, bring that up as a seperate topic on linux-kernel.
Don't bug the poor driver submitter who is just following existing
and accepted practice.
next prev parent reply other threads:[~2008-08-23 9:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 18:40 [PATCH 4/4 2.6.28] cxgb3i - cxgb3i iscsi driver Karen Xie
2008-08-22 19:48 ` Andrew Morton
2008-08-23 8:22 ` Shyam_Iyer
2008-08-23 8:28 ` David Miller
2008-08-23 9:07 ` Shyam_Iyer
2008-08-23 9:29 ` David Miller [this message]
2008-08-23 11:10 ` Shyam_Iyer
2008-08-23 19:31 ` Divy Le Ray
-- strict thread matches above, loose matches on Subject: below --
2008-08-28 4:22 Karen Xie
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=20080823.022934.127206564.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Shyam_Iyer@Dell.com \
--cc=akpm@linux-foundation.org \
--cc=bhua@us.ibm.com \
--cc=daisyc@us.ibm.com \
--cc=divy@chelsio.com \
--cc=dm@chelsio.com \
--cc=jgarzik@pobox.com \
--cc=kxie@chelsio.com \
--cc=leedom@chelsio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=netdev@vger.kernel.org \
--cc=open-iscsi@googlegroups.com \
--cc=rdreier@cisco.com \
--cc=swise@opengridcomputing.com \
--cc=wenxiong@us.ibm.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).