From mboxrd@z Thu Jan  1 00:00:00 1970
From: Al Viro <viro@ZenIV.linux.org.uk>
Subject: Re: key/value-pairs for improved printk()
Date: Sat, 7 Apr 2012 00:58:59 +0100
Message-ID: <20120406235859.GF6589@ZenIV.linux.org.uk>
References: <1333743788.16664.6.camel@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: linux-fsdevel@vger.kernel.org, kay@vrfy.org
To: Dan Luedtke <mail@danrl.de>
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from zeniv.linux.org.uk ([195.92.253.2]:33353 "EHLO
	ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1754540Ab2DFX7C (ORCPT
	<rfc822;linux-fsdevel@vger.kernel.org>);
	Fri, 6 Apr 2012 19:59:02 -0400
Content-Disposition: inline
In-Reply-To: <1333743788.16664.6.camel@localhost>
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

On Fri, Apr 06, 2012 at 10:23:08PM +0200, Dan Luedtke wrote:

> To throw something in the ring, I suggest we append all printk() after
> mounting (e.g. fill_super when autodetecting a fs) with key/value pairs
> like
>   filesystem=mycoolfs
>   device=sda1
>   success=true
> 
> I hope this gets the discussion started!

You've missed the all-important
    bikeshed_colour=

-- 
Those who can - do, those who cannot - sit on the committees discussing how
the increasingly pointless things should be done