From: Huang Ying <ying.huang@intel.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: linux-next: crypto tree build failure
Date: Tue, 20 Jan 2009 11:04:27 +0800 [thread overview]
Message-ID: <1232420667.13948.62.camel@yhuang-dev.sh.intel.com> (raw)
In-Reply-To: <20090120133043.29efee3f.sfr@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 424 bytes --]
Hi, Herbert,
On Tue, 2009-01-20 at 10:30 +0800, Stephen Rothwell wrote:
> Hi Herbert,
>
> Today's linux-next build (x86_64 allmodconfig) failed like this:
>
> arch/x86/crypto/aesni-intel_glue.c:22:21: error: asm/aes.h: No such file or directory
I don't know why. But it seems that asm/aes.h is not included in git,
while it is in my original patch. I will submit a fix patch.
Best Regards,
Huang Ying
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-01-20 3:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 2:30 linux-next: crypto tree build failure Stephen Rothwell
2009-01-20 3:04 ` Huang Ying [this message]
2009-01-20 4:57 ` Herbert Xu
2009-01-20 5:21 ` Herbert Xu
2009-01-20 5:44 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2009-04-22 4:47 Stephen Rothwell
2009-04-22 5:00 ` Herbert Xu
2009-04-22 7:06 ` Stephen Rothwell
2009-04-22 7:36 ` Sebastian Andrzej Siewior
2008-12-04 2:43 Stephen Rothwell
2008-12-04 6:38 ` Herbert Xu
2008-11-11 4:07 Stephen Rothwell
2008-11-11 4:22 ` Herbert Xu
2008-11-11 5:34 ` Stephen Rothwell
2008-08-05 4:02 Stephen Rothwell
2008-08-05 5:36 ` Herbert Xu
2008-08-05 13:33 ` Stephen Rothwell
2008-08-05 14:05 ` Herbert Xu
2008-08-05 14:20 ` Stephen Rothwell
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=1232420667.13948.62.camel@yhuang-dev.sh.intel.com \
--to=ying.huang@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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