Re: RFC: [PATCH 3/5] staging: sep: add sep_crypto.h header

[Greg KH]

On Sun, Feb 27, 2011 at 09:11:32PM -0800, Mark Allyn wrote:
> Signed-off-by: Mark Allyn <mark.a.allyn@xxxxxxxxx>
> ---
>  drivers/staging/sep/sep_crypto.h |  315 ++++++++++++++++++++++++++++++++++++++
>  1 files changed, 315 insertions(+), 0 deletions(-)
>  create mode 100644 drivers/staging/sep/sep_crypto.h
> 
> diff --git a/drivers/staging/sep/sep_crypto.h b/drivers/staging/sep/sep_crypto.h
> new file mode 100644
> index 0000000..10a9425
> --- /dev/null
> +++ b/drivers/staging/sep/sep_crypto.h
> @@ -0,0 +1,315 @@
> +/*
> + *
> + *  sep_crypto.h - Crypto interface structures
> + *
> + *  Copyright(c) 2009,2011 Intel Corporation. All rights reserved.
> + *  Contributions(c) 2009,2010 Discretix. All rights reserved.
> + *
> + *  This program is free software; you can redistribute it and/or modify it
> + *  under the terms of the GNU General Public License as published by the Free
> + *  Software Foundation; version 2 of the License.
> + *
> + *  This program is distributed in the hope that it will be useful, but WITHOUT
> + *  ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
> + *  FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License for
> + *  more details.
> + *
> + *  You should have received a copy of the GNU General Public License along with
> + *  this program; if not, write to the Free Software Foundation, Inc., 59
> + *  Temple Place - Suite 330, Boston, MA  02111-1307, USA.

Ah, you are signing up to track the business office of the FSF for the
next 40+ years and send me patches fixing this file?

Or, if not, don't include this paragraph.

{hint, don't do it...}

> + *  CONTACTS:
> + *
> + *  Mark Allyn		mark.a.allyn@xxxxxxxxx
> + *  Jayant Mangalampalli jayant.mangalampalli@xxxxxxxxx
> + *
> + *  CHANGES:
> + *
> + *  2009.06.26	Initial publish
> + *  2011.02.22  Enable Kernel Crypto

No changes in files.

thanks,

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