All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org,
	Suresh Siddha <suresh.b.siddha@intel.com>,
	Austin Zhang <austin.zhang@intel.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: linux-next: manual merge of the crypto tree
Date: Thu, 28 Aug 2008 09:28:58 +0200	[thread overview]
Message-ID: <20080828072858.GF21875@elte.hu> (raw)
In-Reply-To: <20080825065525.GA23089@gondor.apana.org.au>


* Herbert Xu <herbert@gondor.apana.org.au> wrote:

> > The fixup looks like below.  Maybe the X86_FEATURE_XMM4_2 bits could 
> > also
> 
> Yep looks good.
> 
> > be added in the x86 tree.
> 
> Sure that sounds like a good idea.

they are upstream now:

| commit 2a61812af2e564cba2c8170cf96e1c823210f619
| Author: Austin Zhang <austin_zhang@linux.intel.com>
| Date:   Mon Aug 25 11:14:51 2008 -0400
|
|     x86: add X86_FEATURE_XMM4_2 definitions

so you should be able to pick this up once you merge linus-latest to the 
crypto tree.

	Ingo

  parent reply	other threads:[~2008-08-28  7:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-07  3:35 linux-next: manual merge of the crypto tree Stephen Rothwell
2008-08-07  3:43 ` Herbert Xu
2008-08-25  6:44 ` Stephen Rothwell
2008-08-25  6:53   ` Stephen Rothwell
2008-08-25  6:55   ` Herbert Xu
2008-08-25  7:39     ` Ingo Molnar
2008-08-25  8:05       ` Zhang, Austin
2008-08-27 23:47         ` H. Peter Anvin
2008-08-28  7:27           ` Ingo Molnar
2008-08-28 17:52             ` H. Peter Anvin
2008-08-28  7:28     ` Ingo Molnar [this message]
2008-08-28  7:33       ` 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=20080828072858.GF21875@elte.hu \
    --to=mingo@elte.hu \
    --cc=austin.zhang@intel.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=hpa@zytor.com \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=suresh.b.siddha@intel.com \
    --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 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.