Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Jan Glauber <jan.glauber@de.ibm.com>
To: David Miller <davem@davemloft.net>
Cc: herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: Crypto Update for 2.6.21
Date: Fri, 09 Feb 2007 13:45:07 +0100	[thread overview]
Message-ID: <1171025107.5349.4.camel@localhost.localdomain> (raw)
In-Reply-To: <20070208.152655.104035982.davem@davemloft.net>

On Thu, 2007-02-08 at 15:26 -0800, David Miller wrote:

> There was a minor merge conflict to resolve, because the
> S390 guys removed a bunch of their crypto options from
> crypto/Kconfig in a seperate changeset.  But I'm pretty
> sure I resolved that correctly.

I'll check when the git server works again...

Would it be better if I send patches that also touch common crypto
code to Herbert for integration?

Jan

  reply	other threads:[~2007-02-09 12:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-07 15:47 Crypto Update for 2.6.21 Herbert Xu
2007-02-08 23:26 ` David Miller
2007-02-09 12:45   ` Jan Glauber [this message]
2007-02-09 15:23     ` Herbert Xu

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=1171025107.5349.4.camel@localhost.localdomain \
    --to=jan.glauber@de.ibm.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox