From: "Randy Dunlap" <rdunlap@xenotime.net>
To: "Stephen Rothwell" <sfr@canb.auug.org.au>,
"Mauro Carvalho Chehab" <mchehab@redhat.com>
Cc: linux-next@vger.kernel.org, "LKML" <linux-kernel@vger.kernel.org>,
linux-edac@vger.kernel.org
Subject: Re: linux-next: Tree for Aug 26 (i7core_edac)
Date: Fri, 26 Aug 2011 01:07:50 -0700 [thread overview]
Message-ID: <205ae102ed038641e32cf38c48334f9e.squirrel@xenotime.net> (raw)
In-Reply-To: <20110826150000.302334d0b86c17cd9b89b590@canb.auug.org.au>
On Thu, August 25, 2011 10:00 pm, Stephen Rothwell wrote:
> Hi all,
>
> The powerpc allyesconfig build still fails today.
>
> Changes since 20110825:
on i386:
ERROR: "__udivdi3" [drivers/edac/i7core_edac.ko] undefined!
in both get_sdram_scrub_rate()
and set_sdram_scrub_rate()
--
~Randy
next prev parent reply other threads:[~2011-08-26 8:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-26 5:00 linux-next: Tree for Aug 26 Stephen Rothwell
2011-08-26 8:07 ` Randy Dunlap [this message]
2011-08-26 14:16 ` linux-next: Tree for Aug 26 (i7core_edac) Sedat Dilek
2011-08-26 14:48 ` Borislav Petkov
2011-08-26 17:40 ` Randy Dunlap
2011-08-26 17:54 ` Sedat Dilek
2011-08-26 18:06 ` [PATCH -next] staging: fix rts5139 depends & build Randy Dunlap
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=205ae102ed038641e32cf38c48334f9e.squirrel@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab@redhat.com \
--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
all inboxes | Powered by JetHome®