public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: dhowells@redhat•com, linux-next@vger•kernel.org,
	linux-kernel@vger•kernel.org
Subject: Re: linux-next: build failure after merge of the pekey tree
Date: Fri, 04 Jan 2013 09:48:11 +0000	[thread overview]
Message-ID: <19929.1357292891@warthog.procyon.org.uk> (raw)
In-Reply-To: <20130104120823.6ac07043cfdaad89d9e5b006@canb.auug.org.au>

Stephen Rothwell <sfr@canb•auug.org.au> wrote:

> After merging the pekey tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> ERROR: "modsign_keyring" [crypto/asymmetric_keys/pefile_key_parser.ko] undefined!

Interesting.  That first one isn't due to a missing EXPORT_SYMBOL_GPL().  That
is there.  The problem is that linux/export.h is not #included.  Why does the
C file even build, I wonder?

Anyway, the revised version is pushed.

David

      reply	other threads:[~2013-01-04  9:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-04  1:08 linux-next: build failure after merge of the pekey tree Stephen Rothwell
2013-01-04  9:48 ` David Howells [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=19929.1357292891@warthog.procyon.org.uk \
    --to=dhowells@redhat$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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