From: David Miller <davem@davemloft.net>
To: herbert@gondor.apana.org.au
Cc: torvalds@linux-foundation.org, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: Crypto Update for 2.6.23
Date: Sun, 15 Jul 2007 17:35:29 -0700 (PDT) [thread overview]
Message-ID: <20070715.173529.96681471.davem@davemloft.net> (raw)
In-Reply-To: <20070715131557.GA21255@gondor.apana.org.au>
From: Herbert Xu <herbert@gondor.apana.org.au>
Date: Sun, 15 Jul 2007 21:15:57 +0800
> On Sat, Jul 14, 2007 at 11:48:39PM -0700, David Miller wrote:
> > Herbert can you contact the async_tx author to make sure that
> > his crypto/ bits go through you in the future so that conflicts
> > like this can be avoided?
>
> No problems. This was a once-off because it involved multiple
> conflicts all over the place as Andrew can no doubt attest to :)
I kind of figured as much since it had dependencies on other
subsystems.
prev parent reply other threads:[~2007-07-16 0:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 13:08 Herbert Xu
2007-07-15 6:48 ` David Miller
2007-07-15 13:15 ` Herbert Xu
2007-07-16 0:35 ` David Miller [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=20070715.173529.96681471.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®