From: Paul Bolle <pebolle@tiscali.nl>
To: Stephan Mueller <smueller@chronox.de>
Cc: herbert@gondor.apana.org.au,
Andreas Steffen <andreas.steffen@strongswan.org>,
Theodore Ts'o <tytso@mit.edu>,
Sandy Harris <sandyinchina@gmail.com>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/6] crypto: add jitterentropy RNG
Date: Thu, 23 Apr 2015 16:18:31 +0200 [thread overview]
Message-ID: <1429798711.2927.8.camel@x220> (raw)
In-Reply-To: <3179693.vMYTrm5f8Q@myon.chronox.de>
On Thu, 2015-04-23 at 16:08 +0200, Stephan Mueller wrote:
> Other patches that are in the kernel that I wrote (e.g.
> the crypto/drbg.c) have the same license as above, but use
> MODULE_LICENSE("GPL") -- Thus I would think that leaving it as is should be
> ok.
Why not submit the trivial patches to make the license comment and the
MODULE_LICENSE() macro match in those files too?
Thanks,
Paul Bolle
next prev parent reply other threads:[~2015-04-23 14:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 19:16 [PATCH 0/6] Seeding DRBG with more entropy Stephan Mueller
2015-04-22 19:18 ` [PATCH 1/6] random: Addition of kernel_pool Stephan Mueller
2015-04-22 19:19 ` [PATCH 2/6] random: Async and sync API for accessing kernel_pool Stephan Mueller
2015-04-22 19:20 ` [PATCH 3/6] crypto: drbg - prepare for async seeding Stephan Mueller
2015-04-22 19:24 ` [PATCH 4/6] crypto: drbg - add async seeding operation Stephan Mueller
2015-04-22 19:24 ` [PATCH 5/6] crypto: drbg - use Jitter RNG to obtain seed Stephan Mueller
2015-04-22 19:25 ` [PATCH 6/6] crypto: add jitterentropy RNG Stephan Mueller
2015-04-23 14:05 ` Paul Bolle
2015-04-23 14:08 ` Stephan Mueller
2015-04-23 14:18 ` Paul Bolle [this message]
2015-04-23 14:26 ` Stephan Mueller
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=1429798711.2927.8.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=andreas.steffen@strongswan.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandyinchina@gmail.com \
--cc=smueller@chronox.de \
--cc=tytso@mit.edu \
/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.