Re: [patch] scsi: fix spurious build failures in aic7xxx

[James Bottomley <James.Bottomley@HansenPartnership.com>]

On Sun, 2008-02-03 at 21:05 +0100, Sam Ravnborg wrote:
> On Sun, Feb 03, 2008 at 01:23:42PM -0600, James Bottomley wrote:
> > On Sun, 2008-02-03 at 02:41 -0500, Sam Ravnborg wrote:
> > >         Thanks for testing Ingo.
> > >         
> > >         James - I plan to submit this via kbuild.git in about 10
> > >         hours.
> > >         Let me know if you would like it to go in via scsi and I
> > >         will drop you an updated patch (need to elaboarte a bit more
> > >         in
> > >         the commit message).
> > 
> > Sure, the changes look fine .. and will not conflict with anything
> > pending I currently have.  You can add my acked-by if you want.
> Thanks - will do so.

Great

> > 
> > Please also note the @steeleye.com email address doesn't come to me any
> > more, so this email had to be forwarded.
> OK.
> Can I ask you to fix these:
> Documentation/DocBook/scsi.tmpl:            <email>James.Bottomley@steeleye.com</email>
> Documentation/scsi/scsi_mid_low_api.txt:        James Bottomley <James dot Bottomley at steeleye dot com>

Sure, I'll patch those

> drivers/base/attribute_container.c: * Copyright (c) 2005 - James Bottomley <James.Bottomley@steeleye.com>
> drivers/base/transport_class.c: * Copyright (c) 2005 - James Bottomley <James.Bottomley@steeleye.com>
> drivers/scsi/raid_class.c: * Copyright (c) 2005 - James Bottomley <James.Bottomley@steeleye.com>
> include/linux/attribute_container.h: * Copyright (c) 2005 - James Bottomley <James.Bottomley@steeleye.com>
> include/linux/raid_class.h: * Copyright (c) 2005 - James Bottomley <James.Bottomley@steeleye.com>
> include/linux/transport_class.h: * Copyright (c) 2005 - James Bottomley <James.Bottomley@steeleye.com>

This is less obvious:  The copyrights are historical rather than current
and also, I was at steeleye when I did that work, so it does deserve to
be reflected in the file history.  I know it adds confusion from a whom
do I contact for this file point of view, but it is legally the right
thing to do.

James