All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.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>,
	Linus <torvalds@linux-foundation.org>,
	open-osd development <osd-dev@open-osd.org>,
	NFS list <linux-nfs@vger.kernel.org>
Subject: Re: linux-next: Tree for Jan 5 (exofs or nfs ?)
Date: Sun, 8 Jan 2012 10:36:37 +0200	[thread overview]
Message-ID: <4F095595.4060309@panasas.com> (raw)
In-Reply-To: <4F0644C1.6000405@xenotime.net>

On 01/06/2012 02:48 AM, Randy Dunlap wrote:
> On 01/05/2012 12:12 AM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20120104:
> 
> 
> fs/built-in.o: In function `_write_done':
> objio_osd.c:(.text+0x134971): undefined reference to `ore_check_io'
> fs/built-in.o: In function `_read_done':
> objio_osd.c:(.text+0x134a11): undefined reference to `ore_check_io'
> fs/built-in.o: In function `objio_alloc_io_state':
> objio_osd.c:(.text+0x1353da): undefined reference to `ore_get_rw_state'
> fs/built-in.o: In function `objio_alloc_lseg':
> (.text+0x135724): undefined reference to `ore_verify_layout'
> fs/built-in.o: In function `objio_free_result':
> (.text+0x135966): undefined reference to `ore_put_io_state'
> fs/built-in.o: In function `objio_read_pagelist':
> (.text+0x135be5): undefined reference to `ore_read'
> fs/built-in.o: In function `objio_write_pagelist':
> (.text+0x135d46): undefined reference to `ore_write'
> 
> 
> Full randconfig file is attached.
> 
> 

I have a fix queued for this for linus to pull and Stable@. It should be
in linux-next. Though people reported problems with my git server, im
investigating. Next linux-next should have it.

http://git.open-osd.org/gitweb.cgi?p=linux-open-osd.git;a=commit;h=831c2dc5f47c1dc79c32229d75065ada1dcc66e1

Thanks
Boaz

WARNING: multiple messages have this Message-ID (diff)
From: Boaz Harrosh <bharrosh-C4P08NqkoRlBDgjK7y7TUQ@public.gmane.org>
To: Randy Dunlap <rdunlap-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
Cc: Stephen Rothwell <sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>,
	linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Linus
	<torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
	open-osd development
	<osd-dev-yNzVSZO3znNg9hUCZPvPmw@public.gmane.org>,
	NFS list <linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: linux-next: Tree for Jan 5 (exofs or nfs ?)
Date: Sun, 8 Jan 2012 10:36:37 +0200	[thread overview]
Message-ID: <4F095595.4060309@panasas.com> (raw)
In-Reply-To: <4F0644C1.6000405-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>

On 01/06/2012 02:48 AM, Randy Dunlap wrote:
> On 01/05/2012 12:12 AM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20120104:
> 
> 
> fs/built-in.o: In function `_write_done':
> objio_osd.c:(.text+0x134971): undefined reference to `ore_check_io'
> fs/built-in.o: In function `_read_done':
> objio_osd.c:(.text+0x134a11): undefined reference to `ore_check_io'
> fs/built-in.o: In function `objio_alloc_io_state':
> objio_osd.c:(.text+0x1353da): undefined reference to `ore_get_rw_state'
> fs/built-in.o: In function `objio_alloc_lseg':
> (.text+0x135724): undefined reference to `ore_verify_layout'
> fs/built-in.o: In function `objio_free_result':
> (.text+0x135966): undefined reference to `ore_put_io_state'
> fs/built-in.o: In function `objio_read_pagelist':
> (.text+0x135be5): undefined reference to `ore_read'
> fs/built-in.o: In function `objio_write_pagelist':
> (.text+0x135d46): undefined reference to `ore_write'
> 
> 
> Full randconfig file is attached.
> 
> 

I have a fix queued for this for linus to pull and Stable@. It should be
in linux-next. Though people reported problems with my git server, im
investigating. Next linux-next should have it.

http://git.open-osd.org/gitweb.cgi?p=linux-open-osd.git;a=commit;h=831c2dc5f47c1dc79c32229d75065ada1dcc66e1

Thanks
Boaz
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-01-08  8:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-05  8:12 linux-next: Tree for Jan 5 Stephen Rothwell
2012-01-06  0:18 ` [PATCH -next] fs: fix fs/fs-writeback.c build error Randy Dunlap
2012-01-06 23:01   ` Linus Torvalds
2012-01-07 13:30     ` Wu Fengguang
2012-01-07 18:17       ` Randy Dunlap
2012-01-06  0:48 ` linux-next: Tree for Jan 5 (exofs or nfs ?) Randy Dunlap
2012-01-08  8:36   ` Boaz Harrosh [this message]
2012-01-08  8:36     ` Boaz Harrosh

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=4F095595.4060309@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=osd-dev@open-osd.org \
    --cc=rdunlap@xenotime.net \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.org \
    /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.