All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Walberg <twalberg@comcast.net>
To: Tim Walberg <twalberg@comcast.net>,
	Christoph Hellwig <hch@infradead.org>,
	Linux-kernel <linux-kernel@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	xfs@oss.sgi.com
Subject: Re: xfs compat_ioctl?
Date: Wed, 2 Sep 2009 06:51:23 -0500	[thread overview]
Message-ID: <20090902115123.GA13355@comcast.net> (raw)
In-Reply-To: <20090831190209.GD19343@comcast.net>


[-- Attachment #1.1: Type: text/plain, Size: 1103 bytes --]

Ok, that patch has fixed my issues with xfs_fsr. Now I just need to
pull a new copy of xfs_progs to get the xfs_db alignment issue fix...


		Thanks,
			tw


On 08/31/2009 14:02 -0500, Walberg, Tim wrote:
>>	
>>	
>>	On 08/31/2009 14:49 -0400, Christoph Hellwig wrote:
>>	>>	On Mon, Aug 31, 2009 at 02:48:22PM -0400, Christoph Hellwig wrote:
>>	>>	> On Mon, Aug 31, 2009 at 01:37:51PM -0500, Tim Walberg wrote:
>>	>>	> > Linux sparcy 2.6.30.4-sparcy #2 Sat Aug 1 21:14:46 CDT 2009 sparc64 GNU/Linux
>>	>>	> > sparcy:~# file $(which xfs_fsr)
>>	>>	> > /usr/sbin/xfs_fsr: ELF 32-bit MSB executable, SPARC32PLUS, V8+ Required, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.18, stripped
>>	>>	> 
>>	>>	> I'll take a look at that, thanks.
>>	>>	
>>	>>	Err, sorry - is that with the patch I posted in this thread or without?
>>	End of included message
>>	
>>	
>>	No, that's the generic 2.6.30.4... I can attempt with that patch as well, but
>>	it might be a day or two...
>>	
>>					tw
>>	


End of included message



-- 
twalberg@comcast.net

[-- Attachment #1.2: Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

WARNING: multiple messages have this Message-ID (diff)
From: Tim Walberg <twalberg@comcast.net>
To: Tim Walberg <twalberg@comcast.net>,
	Christoph Hellwig <hch@infradead.org>,
	Linux-kernel <linux-kernel@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	xfs@oss.sgi.com
Subject: Re: xfs compat_ioctl?
Date: Wed, 2 Sep 2009 06:51:23 -0500	[thread overview]
Message-ID: <20090902115123.GA13355@comcast.net> (raw)
In-Reply-To: <20090831190209.GD19343@comcast.net>

[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]

Ok, that patch has fixed my issues with xfs_fsr. Now I just need to
pull a new copy of xfs_progs to get the xfs_db alignment issue fix...


		Thanks,
			tw


On 08/31/2009 14:02 -0500, Walberg, Tim wrote:
>>	
>>	
>>	On 08/31/2009 14:49 -0400, Christoph Hellwig wrote:
>>	>>	On Mon, Aug 31, 2009 at 02:48:22PM -0400, Christoph Hellwig wrote:
>>	>>	> On Mon, Aug 31, 2009 at 01:37:51PM -0500, Tim Walberg wrote:
>>	>>	> > Linux sparcy 2.6.30.4-sparcy #2 Sat Aug 1 21:14:46 CDT 2009 sparc64 GNU/Linux
>>	>>	> > sparcy:~# file $(which xfs_fsr)
>>	>>	> > /usr/sbin/xfs_fsr: ELF 32-bit MSB executable, SPARC32PLUS, V8+ Required, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.18, stripped
>>	>>	> 
>>	>>	> I'll take a look at that, thanks.
>>	>>	
>>	>>	Err, sorry - is that with the patch I posted in this thread or without?
>>	End of included message
>>	
>>	
>>	No, that's the generic 2.6.30.4... I can attempt with that patch as well, but
>>	it might be a day or two...
>>	
>>					tw
>>	


End of included message



-- 
twalberg@comcast.net

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-09-02 11:50 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-31  7:02 xfs compat_ioctl? Michael Tokarev
2009-08-31 12:30 ` Christoph Hellwig
2009-08-31 12:30   ` Christoph Hellwig
2009-08-31 12:57   ` Mark Lord
2009-08-31 12:57     ` Mark Lord
2009-08-31 12:59     ` Michael Tokarev
2009-08-31 12:59       ` Michael Tokarev
2009-08-31 18:14   ` Torsten Kaiser
2009-08-31 18:14     ` Torsten Kaiser
2009-08-31 18:27     ` Christoph Hellwig
2009-08-31 18:27       ` Christoph Hellwig
2009-08-31 18:42       ` Torsten Kaiser
2009-08-31 18:42         ` Torsten Kaiser
2009-09-01 17:00       ` Torsten Kaiser
2009-09-01 17:00         ` Torsten Kaiser
2009-09-01 17:55         ` Eric Sandeen
2009-09-01 17:55           ` Eric Sandeen
2009-08-31 18:37   ` Tim Walberg
2009-08-31 18:37     ` Tim Walberg
2009-08-31 18:48     ` Christoph Hellwig
2009-08-31 18:48       ` Christoph Hellwig
2009-08-31 18:48       ` Christoph Hellwig
2009-08-31 18:49       ` Christoph Hellwig
2009-08-31 18:49         ` Christoph Hellwig
2009-08-31 18:49         ` Christoph Hellwig
2009-08-31 19:02         ` Tim Walberg
2009-08-31 19:02           ` Tim Walberg
2009-09-02 11:51           ` Tim Walberg [this message]
2009-09-02 11:51             ` Tim Walberg

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=20090902115123.GA13355@comcast.net \
    --to=twalberg@comcast.net \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xfs@oss.sgi.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.