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 01:28:30 -0700 (PDT) [thread overview]
Message-ID: <20080823.012830.262443664.davem@davemloft.net> (raw)
In-Reply-To: <46A00B48CC54E4468EF6911F877AC4CA018D73BB@blrx3m10.blr.amer.dell.com>
From: <Shyam_Iyer@Dell.com>
Date: Sat, 23 Aug 2008 13:52:26 +0530
> >I'd suggest that the version number just be removed. It becomes
> meaningless (and often misleading) once a driver is in the mainline
> kernel. People will >update the driver without changing the version
> number. Code external to the driver but which affects it can change.
I totally disagree. I find it very useful when I get a debugging
dump from the user and they have no idea where their kernel
came from nor can figure out how to determine the kernel version.
Sure it might sometimes not get updated for trivial patches that
bypass the maintainer, but the maintainer is always going to bump it
after non-trivial changes.
next prev parent reply other threads:[~2008-08-23 8:28 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 [this message]
2008-08-23 9:07 ` Shyam_Iyer
2008-08-23 9:29 ` David Miller
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.012830.262443664.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).