All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	linux-next@vger.kernel.org, Joe Thornber <dm-devel@redhat.com>,
	Alasdair G Kergon <agk@redhat.com>,
	Mike Snitzer <snitzer@redhat.com>
Subject: Re: mmotm 2012-06-21-16-20 uploaded (dm-thin)
Date: Sun, 24 Jun 2012 08:44:04 -0700	[thread overview]
Message-ID: <4FE735C4.8000308@xenotime.net> (raw)
In-Reply-To: <20120625004425.5efce7fbca77b7cfa086922a@canb.auug.org.au>

On 06/24/2012 07:44 AM, Stephen Rothwell wrote:

> Hi Randy,
> 
> On Fri, 22 Jun 2012 10:26:06 -0700 Randy Dunlap <rdunlap@xenotime.net> wrote:
>>
>> on i386:
>>
>> Apparently from linux-next.patch:
>>
>> drivers/built-in.o: In function `thin_iterate_devices':
>> dm-thin.c:(.text+0x206f07): undefined reference to `__udivdi3'
>> drivers/built-in.o: In function `pool_preresume':
>> dm-thin.c:(.text+0x207863): undefined reference to `__udivdi3'
> 
> I assume that CONFIG_LDBAF is not set and I think this is caused by
> commit ebf5d9e0425c ("Non power of 2 blocksize support is needed to
> properly align thinp IO") from the device-mapper tree.
> 


Correct:
# CONFIG_LBDAF is not set


thanks,
-- 
~Randy

  reply	other threads:[~2012-06-24 15:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-21 23:21 mmotm 2012-06-21-16-20 uploaded akpm
2012-06-21 23:21 ` akpm
2012-06-21 23:21 ` akpm
2012-06-21 23:34 ` Andrew Morton
2012-06-21 23:34   ` Andrew Morton
2012-06-22  7:14 ` Minchan Kim
2012-06-22  7:14   ` Minchan Kim
2012-06-22  8:14 ` viresh kumar
2012-06-22  8:14   ` viresh kumar
2012-06-22  9:23 ` Michal Hocko
2012-06-22  9:23   ` Michal Hocko
2012-06-22 17:26 ` mmotm 2012-06-21-16-20 uploaded (dm-thin) Randy Dunlap
2012-06-22 17:26   ` Randy Dunlap
2012-06-24 14:44   ` Stephen Rothwell
2012-06-24 15:44     ` Randy Dunlap [this message]
2012-06-24 16:55     ` [dm-devel] " Alasdair G Kergon
2012-06-24 18:34       ` Alasdair G Kergon

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=4FE735C4.8000308@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=agk@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=dm-devel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=snitzer@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.