| To: | jgarzik@xxxxxxxxx, netdev@xxxxxxxxxxx |
|---|---|
| Subject: | driver version string changes |
| From: | Don Fry <brazilnut@xxxxxxxxxx> |
| Date: | Mon, 24 May 2004 12:40:38 -0700 (PDT) |
| Sender: | netdev-bounce@xxxxxxxxxxx |
What is the correct approach in dealing with version strings in drivers? For my own sanity, I need to change the version string as I make changes to the driver. Some drivers and the kernel use a nn.nn.nn format while others use nn.nn and others use nn.nnsss, where nn is a number and sss is a character or string. The pcnet32 does a mixture, and I have recently added to that inconsistency. What is the recommendation for version strings in Linux drivers, and what have I not read that already answers this question? -- Don Fry brazilnut@xxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH 2.4.27-pre3] pcnet32: fix bogus carrier errors with 79c973, Don Fry |
|---|---|
| Next by Date: | Re: Kernel BUG: Qos seg. fault, jamal |
| Previous by Thread: | [PATCH 2.4.27-pre3] pcnet32: fix bogus carrier errors with 79c973, Don Fry |
| Next by Thread: | [PATCH] update Documentation/networking/bridge.txt, Stephen Hemminger |
| Indexes: | [Date] [Thread] [Top] [All Lists] |