All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Mark Allyn <mark.a.allyn@intel.com>
Cc: linux-kernel@vger.kernel.org, alan@linux.intel.com
Subject: Re: RFC: [PATCH 3/5] staging: sep: add sep_crypto.h header
Date: Mon, 28 Feb 2011 13:19:02 -0800	[thread overview]
Message-ID: <20110228211902.GC8851@kroah.com> (raw)
In-Reply-To: <1298869892-4357-1-git-send-email-mark.a.allyn@intel.com>

On Sun, Feb 27, 2011 at 09:11:32PM -0800, Mark Allyn wrote:
> Signed-off-by: Mark Allyn <mark.a.allyn@intel.com>
> ---
>  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@intel.com
> + *  Jayant Mangalampalli jayant.mangalampalli@intel.com
> + *
> + *  CHANGES:
> + *
> + *  2009.06.26	Initial publish
> + *  2011.02.22  Enable Kernel Crypto

No changes in files.

thanks,

greg k-h

      reply	other threads:[~2011-02-28 21:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-28  5:11 RFC: [PATCH 3/5] staging: sep: add sep_crypto.h header Mark Allyn
2011-02-28 21:19 ` Greg KH [this message]

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=20110228211902.GC8851@kroah.com \
    --to=greg@kroah.com \
    --cc=alan@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.a.allyn@intel.com \
    /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.