From: Diego Calleja <diegocg@gmail.com>
To: Daniel Phillips <phillips@phunq.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
tux3@tux3.org, linux-kernel@vger.kernel.org
Subject: Re: [Tux3] Tux3 report: Tux3 Git tree available
Date: Thu, 12 Mar 2009 16:30:19 +0100 [thread overview]
Message-ID: <200903121630.19648.diegocg@gmail.com> (raw)
In-Reply-To: <200903120133.02645.phillips@phunq.net>
On Jueves 12 Marzo 2009 09:33:02 Daniel Phillips escribió:
> > umm, it _is_ primarily kernel code, after all. So it seems appropriate
> > to use BUG_ON() and printk(), etc and to provide versions of those for
> > the userspace incarnation?
>
> Will do.
btrfs-progs also runs some btrfs kernel code in userspace, tux3 could reuse
their "compatibility layer", it can be found at btrfs-progs/kerncompat.h
next prev parent reply other threads:[~2009-03-12 15:28 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 16:25 Tux3 report: Tux3 Git tree available Daniel Phillips
2009-03-11 18:42 ` Andrew Morton
2009-03-12 5:38 ` [Tux3] " Daniel Phillips
2009-03-12 6:07 ` Andrew Morton
2009-03-12 8:33 ` Daniel Phillips
2009-03-12 8:47 ` Nick Piggin
2009-03-12 9:00 ` Daniel Phillips
2009-03-12 9:10 ` Nick Piggin
2009-03-12 10:15 ` Daniel Phillips
2009-03-12 11:03 ` Nick Piggin
2009-03-12 12:24 ` Daniel Phillips
2009-03-12 12:32 ` Matthew Wilcox
2009-03-12 12:45 ` Nick Piggin
2009-03-12 12:45 ` Nick Piggin
2009-03-12 13:12 ` [Tux3] " Daniel Phillips
2009-03-12 13:06 ` Daniel Phillips
2009-03-12 13:04 ` Nick Piggin
2009-03-12 13:04 ` Nick Piggin
2009-03-12 13:59 ` [Tux3] " Matthew Wilcox
2009-03-12 14:19 ` Nick Piggin
2009-03-15 3:24 ` Daniel Phillips
2009-03-15 3:24 ` Daniel Phillips
2009-03-15 3:50 ` [Tux3] " Nick Piggin
2009-03-15 4:08 ` Daniel Phillips
2009-03-15 4:08 ` Daniel Phillips
2009-03-15 4:14 ` [Tux3] " Nick Piggin
2009-03-15 2:41 ` Daniel Phillips
2009-03-15 3:45 ` Nick Piggin
2009-03-15 21:44 ` Theodore Tso
2009-03-15 22:41 ` Daniel Phillips
2009-03-16 10:32 ` Nick Piggin
2009-03-16 5:12 ` Dave Chinner
2009-03-16 5:12 ` Dave Chinner
2009-03-16 6:38 ` Theodore Tso
2009-03-16 6:38 ` Theodore Tso
2009-03-16 10:14 ` Nick Piggin
2009-03-16 10:14 ` Nick Piggin
2009-03-12 17:06 ` [Tux3] " Theodore Tso
2009-03-13 9:32 ` Nick Piggin
2009-03-12 17:00 ` OGAWA Hirofumi
2009-03-15 3:54 ` Daniel Phillips
2009-03-12 9:47 ` Sam Ravnborg
2009-03-12 10:25 ` Daniel Phillips
2009-03-12 15:30 ` Diego Calleja [this message]
2009-03-12 16:54 ` OGAWA Hirofumi
2009-03-15 3:36 ` Daniel Phillips
2009-03-15 4:26 ` OGAWA Hirofumi
2009-03-12 13:24 ` Andi Kleen
2009-03-12 21:24 ` [Tux3] " Daniel Phillips
2009-03-12 23:38 ` Andi Kleen
2009-03-15 3:03 ` Daniel Phillips
2009-03-12 21:02 ` Roland Dreier
2009-03-15 4:02 ` Daniel Phillips
2009-03-12 16:18 ` OGAWA Hirofumi
2009-03-12 20:02 ` Andrew Morton
2009-03-12 20:46 ` OGAWA Hirofumi
2009-03-15 3:58 ` Daniel Phillips
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=200903121630.19648.diegocg@gmail.com \
--to=diegocg@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@phunq.net \
--cc=tux3@tux3.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.