[lkml]   [2010]   [Oct]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: Firmware versioning best practices: ath3k-2.fw rename or replace ath3k-1.fw ?
    On Fri, Oct 08, 2010 at 11:15:08AM -0700, Luis R. Rodriguez wrote:
    > On Fri, Oct 08, 2010 at 10:27:36AM -0700, Suraj Sumangala wrote:
    > > Marcel had answered me before. It makes sense to have same file name.
    > > Other ways we end up changing the driver whenever there is a firmware
    > > change.
    > > > I last tried to document a thread we had over this here:
    > > >
    > > >
    > > >
    > Thanks, I've updated that link above to document bug fixing does not require
    > a filename change.

    I don't really understand why you would not want to change the code revision
    part of the filename.

    I totally agree that you don't want to change the driver every time the
    firmware gets a bug fix, but wasn't that the whole point of splitting the name
    into API and code revisions portions, and symlinking the file to one that just
    has the API version?

    What's the issue with using the process as originally documented?

    - Henry

     \ /
      Last update: 2010-10-12 23:27    [W:0.024 / U:2.140 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site