[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200805021052.44076.chris.mason@oracle.com>
Date: Fri, 2 May 2008 10:52:43 -0400
From: Chris Mason <chris.mason@...cle.com>
To: Matthew Wilcox <matthew@....cx>
Cc: jeffschroeder@...puter.org, Jan Engelhardt <jengelh@...ozas.de>,
Jeff Mahoney <jeffm@...e.com>,
Tim Gardner <tim.gardner@...onical.com>,
linux-fsdevel@...r.kernel.org, kernel-team@...ts.ubuntu.com,
linux-kernel@...r.kernel.org, linux-btrfs@...r.kernel.org,
John Johansen <jjohansen@...e.de>
Subject: Re: Btrfs v0.14 Released
On Friday 02 May 2008, Matthew Wilcox wrote:
> On Fri, May 02, 2008 at 10:34:07AM -0400, Chris Mason wrote:
> > Thanks, but this uses CONFIG_SECURITY_APPARMOR which isn't enough to tell
> > if the kernel has the patch. Lets go back to Jeff's suse patch:
>
> Do we really need to support kernels compiled with the apparmour patch
> applied but not enabled? That would be a custom kernel build, and I get
> the impression that people Just Don't Do That -- if they want a newer
> kernel, they fetch one from kernel.org. Maybe I'm wrong though.
Yeah, if there's no better test I'll just use the one for the apparmor config
(and stop spamming l-k with this btrfs specific stuff).
-chris
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists