From: Tim Walberg <twalberg@comcast.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: Tim Walberg <twalberg@comcast.net>,
Michael Tokarev <mjt@tls.msk.ru>,
Linux-kernel <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
xfs@oss.sgi.com
Subject: Re: xfs compat_ioctl?
Date: Mon, 31 Aug 2009 14:02:09 -0500 [thread overview]
Message-ID: <20090831190209.GD19343@comcast.net> (raw)
In-Reply-To: <20090831184918.GB10393@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
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
--
+----------------------+
| Tim Walberg |
| 830 Carriage Dr. |
| Algonquin, IL 60102 |
| twalberg@comcast.net |
+----------------------+
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-08-31 19:02 UTC|newest]
Thread overview: 14+ 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:57 ` Mark Lord
2009-08-31 12:59 ` Michael Tokarev
2009-08-31 18:14 ` Torsten Kaiser
2009-08-31 18:27 ` Christoph Hellwig
2009-08-31 18:42 ` Torsten Kaiser
2009-09-01 17:00 ` Torsten Kaiser
2009-09-01 17:55 ` Eric Sandeen
2009-08-31 18:37 ` Tim Walberg
2009-08-31 18:48 ` Christoph Hellwig
2009-08-31 18:49 ` Christoph Hellwig
2009-08-31 19:02 ` 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=20090831190209.GD19343@comcast.net \
--to=twalberg@comcast.net \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).