From: Chris Mason <chris.mason@oracle.com>
To: Tim Gelter <tgelter@gurulabs.com>
Cc: Ahmed Kamal <email.ahmedkamal@googlemail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: Problems building btrfs
Date: Fri, 18 Jul 2008 14:20:53 -0400 [thread overview]
Message-ID: <1216405254.6932.41.camel@think.oraclecorp.com> (raw)
In-Reply-To: <4880C69B.7050301@gurulabs.com>
On Fri, 2008-07-18 at 10:36 -0600, Tim Gelter wrote:
> Hello all,
> I've been silently following the development of btrfs for a while now.
> After checking out and building the kernel module, I am unable to insmod
> it. It complains that it's not of a valid type. Any ideas?
> -Tim
>
Hello,
Could you please cut n' paste the error messages, as well as anything
from the kernel dmesg.
-chris
next prev parent reply other threads:[~2008-07-18 18:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3da3b5b40807160139w4b8e3474te113980d0086ba9c@mail.gmail.com>
2008-07-16 9:06 ` QA suite plans Ahmed Kamal
2008-07-16 12:05 ` Josef Bacik
2008-07-16 13:22 ` Ahmed Kamal
2008-07-17 14:25 ` Miguel Sousa Filipe
2008-07-18 16:30 ` Ahmed Kamal
2008-07-18 16:36 ` Tim Gelter
2008-07-18 18:20 ` Chris Mason [this message]
2008-07-18 18:51 ` Problems building btrfs tgelter
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=1216405254.6932.41.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=email.ahmedkamal@googlemail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=tgelter@gurulabs.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