Date: Mon, 26 Sep 2005 13:13:31 -0700
From: Greg KH <greg@kroah.com>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Dave Jones <davej@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: usb-snd-audio breakage
Message-ID: <20050926201331.GA18480@kroah.com>
References: <9e4733910509251927484a70c7@mail.gmail.com> <9e4733910509251943277f077a@mail.gmail.com> <20050926033805.GB22376@redhat.com> <9e473391050926063264010349@mail.gmail.com> <20050926150709.GB15781@kroah.com> <9e473391050926085476c1582d@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <9e473391050926085476c1582d@mail.gmail.com>
User-Agent: Mutt/1.5.11
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1171
Lines: 26

On Mon, Sep 26, 2005 at 11:54:31AM -0400, Jon Smirl wrote:
> On 9/26/05, Greg KH <greg@kroah.com> wrote:
> > After thinking about this for a while, and seeing all of the different
> > iterations that the sysfs-whitespace-cleanup patch went through, I do
> > not want to add this to sysfs.  It is very easy to add this to a
> > subsystem, or even provide a generic function to do this if you want to
> > (I'd be glad to add that to the sysfs core) but it's not for the core of
> > sysfs to do for all files.
> 
> I went through the iterations because I hadn't thought about the case
> where people were assigning multi-line CR terminated values to sysfs
> attributes and then using multiple reads to process the assignments
> one line at a time. I had thought that sysfs was only supposed to
> allow the assignment of single values.

Yes, that is "heavily encouraged" to be the case.  But as you found
out...

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/