From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Neil Brown <neilb@suse.de>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-raid@vger.kernel.org
Subject: Re: linux-next: Tree for April 21 (md/raid456)
Date: Thu, 21 Apr 2011 07:41:13 -0700 [thread overview]
Message-ID: <20110421074113.5a0410fc.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20110421132045.5af1b953.sfr@canb.auug.org.au>
On Thu, 21 Apr 2011 13:20:45 +1000 Stephen Rothwell wrote:
> Changes since 20110420:
on i386:
ERROR: "__udivdi3" [drivers/md/raid456.ko] undefined!
in raid45_takeover_raid0()
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-04-21 14:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 3:20 linux-next: Tree for April 21 Stephen Rothwell
2011-04-21 14:41 ` Randy Dunlap [this message]
2011-04-21 15:51 ` linux-next: Tree for April 21 (i82975x_edac) Randy Dunlap
2011-04-23 8:21 ` Arvind R
2011-04-23 15:45 ` Randy Dunlap
2011-04-24 6:29 ` Arvind R
2011-04-25 2:13 ` Randy Dunlap
2011-04-25 5:51 ` Arvind R
2011-04-25 7:00 ` Jason Uhlenkott
2011-04-21 16:09 ` [PATCH -next] kvm: fix const value warning on i386 Randy Dunlap
2011-04-24 7:12 ` Avi Kivity
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=20110421074113.5a0410fc.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--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