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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1202069700.3318.100.camel@localhost.localdomain>
Date:	Sun, 03 Feb 2008 14:15:00 -0600
From:	James Bottomley <James.Bottomley@...senPartnership.com>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
	Jens Axboe <jens.axboe@...cle.com>,
	Hannes Reinecke <hare@...e.de>, Christoph Hellwig <hch@....de>
Subject: Re: [patch] scsi: fix spurious build failures in aic7xxx

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@...eleye.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@...eleye.com>
> drivers/base/transport_class.c: * Copyright (c) 2005 - James Bottomley <James.Bottomley@...eleye.com>
> drivers/scsi/raid_class.c: * Copyright (c) 2005 - James Bottomley <James.Bottomley@...eleye.com>
> include/linux/attribute_container.h: * Copyright (c) 2005 - James Bottomley <James.Bottomley@...eleye.com>
> include/linux/raid_class.h: * Copyright (c) 2005 - James Bottomley <James.Bottomley@...eleye.com>
> include/linux/transport_class.h: * Copyright (c) 2005 - James Bottomley <James.Bottomley@...eleye.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


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/