From: Chuck Ebbert <cebbert@redhat.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>,
Ingo Molnar <mingo@elte.hu>,
linux-crypto@vger.kernel.org, tglx@linutronix.de,
mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
mail@tobiasvolk.de
Subject: Re: enable padlock on x86_64
Date: Mon, 20 Apr 2009 18:09:31 -0400 [thread overview]
Message-ID: <20090420180931.7bd7ff02@dhcp-100-2-144.bos.redhat.com> (raw)
In-Reply-To: <20090314132420.GB6080@gondor.apana.org.au>
On Sat, 14 Mar 2009 21:24:20 +0800
Herbert Xu <herbert@gondor.apana.org.au> wrote:
> On Sat, Mar 14, 2009 at 12:53:07PM +0100, Sebastian Andrzej Siewior wrote:
> >
> > Yep, it is fine.
> > #1 in, #2 not will not result in any difference to what we have now.
> > #2 in, #1 not will result in "padlock not detected" while loading the
> > module and -ENODEV.
>
> Let's merge #1 right now and I'll pick up #2 once #1 shows up
> in linux-net.
>
#1 is in 2.6.30-rc now but I don't see #2 pending anywhere.
next prev parent reply other threads:[~2009-04-20 22:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <49B83002.9040705@tobiasvolk.de>
2009-03-14 11:24 ` Sebastian Andrzej Siewior
2009-03-14 11:47 ` Ingo Molnar
2009-03-14 11:53 ` Sebastian Andrzej Siewior
2009-03-14 13:24 ` Herbert Xu
2009-04-20 22:09 ` Chuck Ebbert [this message]
2009-04-21 5:59 ` Herbert Xu
2009-03-14 11:24 ` [PATCH 1/2] x86/centaur: merge 32 & 64 bit version Sebastian Andrzej Siewior
2009-03-14 15:30 ` [tip:x86/cpu] " Sebastian Andrzej Siewior
2009-03-14 11:24 ` [PATCH 2/2] crypto/padlock: enable on x86_64 Sebastian Andrzej Siewior
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=20090420180931.7bd7ff02@dhcp-100-2-144.bos.redhat.com \
--to=cebbert@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=hpa@zytor.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@tobiasvolk.de \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=sebastian@breakpoint.cc \
--cc=tglx@linutronix.de \
/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®