netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matt Domsch <Matt_Domsch@dell.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Michael Wu <flamingice@sourmilk.net>,
	Christoph Hellwig <hch@infradead.org>,
	James Ketrenos <jketreno@linux.intel.com>,
	NetDev <netdev@vger.kernel.org>,
	ieee80211-devel@lists.sourceforge.net,
	Andrew Morton <akpm@osdl.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: ieee80211 updates
Date: Mon, 19 Sep 2005 17:00:56 -0500	[thread overview]
Message-ID: <20050919220056.GB3916@lists.us.dell.com> (raw)
In-Reply-To: <432E4F7A.9040605@pobox.com>

On Mon, Sep 19, 2005 at 01:41:14AM -0400, Jeff Garzik wrote:
> Michael Wu wrote:
> >If it has a version, then only the maintainer can submit patches - 
> 
> False.  Presence of an optional label in source code files does not 
> change the fundamental rules of open source, or the processes 
> surrounding patch merging in the Linux kernel.  Anybody who feels the 
> version number should be changed is welcome to submit a patch.  And a 
> reviewer along the line is welcome to reject such a patch, if they think 
> it is unwarranted.
> 
> >otherwise the
> >version is useless for identifying what code you're running. (unless other
> 
> False.  We have plenty of examples of slower-moving drivers where 
> community consensus often dictates a version number change.


This is also the reason for the 'srcversion' field available in
modinfo.  This is a CRC across the source code for a given module (not
counting #include<*>, but counting #include "*").  The version field
may not change, but if anything really cares about a particular source
code copy, and that it hasn't been patched, but the version field not
updated, they can see that.

Thanks to Rusty for implementing this.

Thanks,
Matt

-- 
Matt Domsch
Software Architect
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com

      reply	other threads:[~2005-09-19 22:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4327625D.10808@linux.intel.com>
     [not found] ` <20050914105409.GB30645@infradead.org>
     [not found]   ` <43285ADF.5030506@linux.intel.com>
     [not found]     ` <20050917092846.GA14083@infradead.org>
     [not found]       ` <432E1069.8010102@pobox.com>
     [not found]         ` <20050919004450.16m2d1hn7les0o00@www.sourmilk.net>
2005-09-19  5:41           ` ieee80211 updates Jeff Garzik
2005-09-19 22:00             ` Matt Domsch [this message]

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=20050919220056.GB3916@lists.us.dell.com \
    --to=matt_domsch@dell.com \
    --cc=akpm@osdl.org \
    --cc=flamingice@sourmilk.net \
    --cc=hch@infradead.org \
    --cc=ieee80211-devel@lists.sourceforge.net \
    --cc=jgarzik@pobox.com \
    --cc=jketreno@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --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).