All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rik van Riel <riel@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: research@subreption.com, linux-kernel@vger.kernel.org,
	pageexec@freemail.hu, linux-mm@kvack.org, torvalds@osdl.org,
	alan@lxorguk.ukuu.org.uk, linux-crypto@vger.kernel.org,
	herbert@gondor.apana.org.au
Subject: Re: [PATCH] Use kzfree in crypto API context initialization and key/iv handling
Date: Sun, 31 May 2009 10:38:52 -0400	[thread overview]
Message-ID: <4A22967C.3080304@redhat.com> (raw)
In-Reply-To: <20090530.230213.73434433.davem@davemloft.net>

David Miller wrote:
> From: "Larry H." <research@subreption.com>
> Date: Sat, 30 May 2009 19:57:20 -0700
> 
>> [PATCH] Use kzfree in crypto API context initialization and key/iv handling
> 
> Thanks for not CC:ing the crypto list, and also not CC:'ing the
> crypto maintainer.
> 
> Your submissions leave a lot to be desired, on every level.

That's a pretty roundabout way of saying "I have no
technical objections" :)

-- 
All rights reversed.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Rik van Riel <riel@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: research@subreption.com, linux-kernel@vger.kernel.org,
	pageexec@freemail.hu, linux-mm@kvack.org, torvalds@osdl.org,
	alan@lxorguk.ukuu.org.uk, linux-crypto@vger.kernel.org,
	herbert@gondor.apana.org.au
Subject: Re: [PATCH] Use kzfree in crypto API context initialization and key/iv handling
Date: Sun, 31 May 2009 10:38:52 -0400	[thread overview]
Message-ID: <4A22967C.3080304@redhat.com> (raw)
In-Reply-To: <20090530.230213.73434433.davem@davemloft.net>

David Miller wrote:
> From: "Larry H." <research@subreption.com>
> Date: Sat, 30 May 2009 19:57:20 -0700
> 
>> [PATCH] Use kzfree in crypto API context initialization and key/iv handling
> 
> Thanks for not CC:ing the crypto list, and also not CC:'ing the
> crypto maintainer.
> 
> Your submissions leave a lot to be desired, on every level.

That's a pretty roundabout way of saying "I have no
technical objections" :)

-- 
All rights reversed.

  reply	other threads:[~2009-05-31 14:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-31  2:57 [PATCH] Use kzfree in crypto API context initialization and key/iv handling Larry H.
2009-05-31  2:57 ` Larry H.
2009-05-31  6:02 ` David Miller
2009-05-31  6:02   ` David Miller
2009-05-31 14:38   ` Rik van Riel [this message]
2009-05-31 14:38     ` Rik van Riel
2009-06-01  4:46     ` David Miller
2009-06-01  4:46       ` David Miller
2009-06-01  4:48       ` Herbert Xu
2009-06-01  4:48         ` Herbert Xu
2009-06-01  7:58         ` Alan Cox
2009-06-01  7:58           ` Alan Cox
2009-06-01 12:33           ` Herbert Xu
2009-06-01 12:33             ` Herbert Xu
2009-05-31 14:38 ` Rik van Riel
2009-05-31 14:38   ` Rik van Riel

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=4A22967C.3080304@redhat.com \
    --to=riel@redhat.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pageexec@freemail.hu \
    --cc=research@subreption.com \
    --cc=torvalds@osdl.org \
    /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.