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: Mon, 25 Aug 2008 09:39:26 +0200 [thread overview]
Message-ID: <20080825073926.GA9147@elte.hu> (raw)
In-Reply-To: <20080825065525.GA23089@gondor.apana.org.au>
* Herbert Xu <herbert@gondor.apana.org.au> wrote:
> On Mon, Aug 25, 2008 at 04:44:18PM +1000, Stephen Rothwell wrote:
> >
> > On Thu, 7 Aug 2008 13:35:25 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > >
> > > Today's linux-next merge of the crypto tree got a conflict in
> > > include/asm-x86/cpufeature.h between commit
> > > 32e1d0a0651004f5fe47f85a2a5c725ad579a90c ("x64, x2apic/intr-remap: cpuid
> > > bits for x2apic feature") from the x86 tree and commit
> > > 1f4f8a5d7935c81b5b3c7601ec9ac021db30ba4f ("crypto: crc32c - Use Intel
> > > CRC32 instruction") from the crypto tree.
> > >
> > > Just simple overlapping additions. I added both of them and can carry
> > > the fixup.
> >
> > This now also conflicts with commit
> > a648bf4632628c787abb0514277f2a231fca39ca ("x86, xsave: xsave cpuid
> > feature bits") from the x86 tree.
> >
> > 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.
new x86 feature bits should definitely show up in the x86 tree too.
Could you please send a standalone patch that only touches the .h file,
which could be applied to v2.6.27 as well? Thanks,
Ingo
next prev parent reply other threads:[~2008-08-25 7:39 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 [this message]
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
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=20080825073926.GA9147@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).