From: Dave Jones <davej@redhat.com>
To: Christoph Hellwig <hch@infradead.org>,
Fruhwirth Clemens <clemens-dated-1085311555.6f4f@endorphin.org>,
linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] AES i586 optimized
Date: Thu, 13 May 2004 13:37:39 +0100 [thread overview]
Message-ID: <20040513123739.GA6046@redhat.com> (raw)
In-Reply-To: <20040513131850.A9466@infradead.org>
On Thu, May 13, 2004 at 01:18:50PM +0100, Christoph Hellwig wrote:
> On Thu, May 13, 2004 at 01:25:55PM +0200, Fruhwirth Clemens wrote:
> > > advertisment clause, so GPL-incompatible.
> >
> > Standard BSD license text. Listed as GPL-compatible by FSF.
>
> Thanks, braino. Didn't notice the and/or
>
Given the and/or, could we drop this chunk and put it somewhere
more suitable, like Documentation/ (or even the Kconfig at a push) ?
I don't think we include any other terms/license agreements
in binary form (other than MODULE_LICENSE() stuff), so why should
we special case this one?
Dave
+copyright:
+ .ascii " \000"
+ .ascii "Copyright (c) 2001, Dr Brian Gladman <brg@gladman.uk.net>, Worcester, UK.\000"
+ .ascii "All rights reserved.\000"
+ .ascii " \000"
+ .ascii "TERMS\000"
+ .ascii " \000"
+ .ascii " Redistribution and use in source and binary forms, with or without\000"
+ .ascii " modification, are permitted subject to the following conditions:\000"
+ .ascii " \000"
+ .ascii " 1. Redistributions of source code must retain the above copyright\000"
+ .ascii " notice, this list of conditions and the following disclaimer.\000"
+ .ascii " \000"
+ .ascii " 2. Redistributions in binary form must reproduce the above copyright\000"
+ .ascii " notice, this list of conditions and the following disclaimer in the\000"
+ .ascii " documentation and/or other materials provided with the distribution.\000"
+ .ascii " \000"
+ .ascii " 3. The copyright holder's name must not be used to endorse or promote\000"
+ .ascii " any products derived from this software without his specific prior\000"
+ .ascii " written permission.\000"
+ .ascii " \000"
+ .ascii " This software is provided 'as is' with no express or implied warranties\000"
+ .ascii " of correctness or fitness for purpose.\000"
+ .ascii " \000"
next prev parent reply other threads:[~2004-05-13 12:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-13 11:01 [PATCH] AES i586 optimized Fruhwirth Clemens
2004-05-13 11:07 ` Andrew Morton
2004-05-13 11:42 ` Fruhwirth Clemens
2004-05-13 14:05 ` Felipe Alfaro Solana
2004-05-13 15:29 ` [PATCH] AES i586 optimized (oops) Felipe Alfaro Solana
2004-05-13 19:27 ` Felipe Alfaro Solana
2004-05-13 12:34 ` [PATCH] AES i586 optimized Fruhwirth Clemens
2004-05-13 11:13 ` Christoph Hellwig
2004-05-13 11:25 ` Fruhwirth Clemens
2004-05-13 12:18 ` Christoph Hellwig
2004-05-13 12:37 ` Dave Jones [this message]
2004-05-13 13:24 ` Christophe Saout
2004-05-13 15:09 ` James Morris
2004-05-13 15:23 ` James Morris
2004-05-13 22:23 ` Felipe Alfaro Solana
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=20040513123739.GA6046@redhat.com \
--to=davej@redhat.com \
--cc=akpm@osdl.org \
--cc=clemens-dated-1085311555.6f4f@endorphin.org \
--cc=hch@infradead.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.