public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	linux-crypto@vger.kernel.org
Subject: Re: linux-next: Tree for July 2 (crypto/hifn_795x)
Date: Mon, 02 Jul 2012 09:27:30 -0700	[thread overview]
Message-ID: <4FF1CBF2.8060303@xenotime.net> (raw)
In-Reply-To: <20120702172334.2618cae84cc57b4ec5a63ed7@canb.auug.org.au>

On 07/02/2012 12:23 AM, Stephen Rothwell wrote:

> Hi all,
> 
> Changes since 20120629:
> 


on i386:


ERROR: "__divdi3" [drivers/crypto/hifn_795x.ko] undefined!


-- 
~Randy

  parent reply	other threads:[~2012-07-02 16:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-02  7:23 linux-next: Tree for July 2 Stephen Rothwell
2012-07-02 16:19 ` linux-next: Tree for July 2 (pktgen) Randy Dunlap
2012-07-02 16:27 ` Randy Dunlap [this message]
2012-07-06 20:32   ` linux-next: Tree for July 2 (crypto/hifn_795x) Geert Uytterhoeven
2012-07-09 17:54   ` Jussi Kivilinna
2012-07-09 21:40     ` Randy Dunlap
2012-07-30  7:49       ` 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=4FF1CBF2.8060303@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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