From: Alan Cox <alan@linux.intel.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Feb 10 (sep_crypto)
Date: Sat, 11 Feb 2012 10:43:20 +0000 [thread overview]
Message-ID: <20120211104320.1ba5d23d@bob.linux.org.uk> (raw)
In-Reply-To: <4F35DB8D.8090706@xenotime.net>
On Fri, 10 Feb 2012 19:07:57 -0800
Randy Dunlap <rdunlap@xenotime.net> wrote:
> On 02/09/2012 10:19 PM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20120209:
>
> > ----------------------------------------------------------------------------
>
>
> on x86_64:
>
> sep_crypto.c:(.text+0x155d32): undefined reference to
> `ablkcipher_walk_phys' drivers/built-in.o: In function `sep_dequeuer':
Thanks.. Will take a look Monday. I think I know what that is.
Alan
prev parent reply other threads:[~2012-02-11 10:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 6:19 linux-next: Tree for Feb 10 Stephen Rothwell
2012-02-11 3:04 ` linux-next: Tree for Feb 10 (drivers/video/backlight/ot200_bl) Randy Dunlap
2012-02-11 3:07 ` linux-next: Tree for Feb 10 (sep_crypto) Randy Dunlap
2012-02-11 10:43 ` Alan Cox [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=20120211104320.1ba5d23d@bob.linux.org.uk \
--to=alan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--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;
as well as URLs for NNTP newsgroup(s).