From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Joe Perches <joe@perches.com>
Cc: greg@kroah.com, linux-kernel@vger.kernel.org,
Mark Allyn <mark.a.allyn@intel.com>
Subject: Re: [PATCH] sep: SEP update
Date: Thu, 29 Dec 2011 12:25:02 +0000 [thread overview]
Message-ID: <20111229122502.540c6f7f@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <1325110478.16729.7.camel@joe2Laptop>
On Wed, 28 Dec 2011 14:14:38 -0800
Joe Perches <joe@perches.com> wrote:
> On Wed, 2011-12-28 at 17:37 +0000, Alan Cox wrote:
> > From: Mark Allyn <mark.a.allyn@intel.com>
> > The new driver supports the kernel crypto layer, passes the coding style checks,
> > passes human taste checks and has proper kernel-doc formatted comments.
>
> These are just taste comments.
Not so sure about the switch case one but the others I concur - I'll send
Greg a follow up patch once the main one is merged.
Alan
prev parent reply other threads:[~2011-12-29 12:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-28 17:37 [PATCH] sep: SEP update Alan Cox
2011-12-28 22:14 ` Joe Perches
2011-12-29 12:25 ` Alan Cox [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=20111229122502.540c6f7f@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=greg@kroah.com \
--cc=joe@perches.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox