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 4/5] staging: sep: update sep_main.c for kernel crypto operation
Date: Mon, 28 Feb 2011 13:19:25 -0800 [thread overview]
Message-ID: <20110228211925.GD8851@kroah.com> (raw)
In-Reply-To: <1298869909-4394-1-git-send-email-mark.a.allyn@intel.com>
On Sun, Feb 27, 2011 at 09:11:49PM -0800, Mark Allyn wrote:
> These changes include new functions required by the sep_crypto.c
> file (to be added in subsequent patch) as well as alterations
> in interrupt handler.
You just broke the build. Don't do that.
greg k-h
prev parent 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 4/5] staging: sep: update sep_main.c for kernel crypto operation 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=20110228211925.GD8851@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.