From: Jon Smirl <jonsmirl@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: Dave Jones <davej@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: usb-snd-audio breakage
Date: Mon, 26 Sep 2005 11:54:31 -0400 [thread overview]
Message-ID: <9e473391050926085476c1582d@mail.gmail.com> (raw)
In-Reply-To: <20050926150709.GB15781@kroah.com>
On 9/26/05, Greg KH <greg@kroah.com> wrote:
> On Mon, Sep 26, 2005 at 09:32:43AM -0400, Jon Smirl wrote:
> > So module
>
> That's up to that maintainer.
>
> > and proc code
>
> That is not true at all.
In one of the older threads about this someone pointed out two places
in /proc where it is done too. I tried searching for the message but I
can't find it.
> > will strip white space, but sysfs won't strip white space. Where is
> > the consistency?
>
> If you want to strip whitespace for all of your subsystem's sysfs files,
> a single function call will do this.
>
> 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.
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2005-09-26 15:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-26 2:27 usb-snd-audio breakage Jon Smirl
2005-09-26 2:43 ` Jon Smirl
2005-09-26 3:38 ` Dave Jones
2005-09-26 13:32 ` Jon Smirl
2005-09-26 15:07 ` Greg KH
2005-09-26 15:54 ` Jon Smirl [this message]
2005-09-26 20:13 ` Greg KH
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=9e473391050926085476c1582d@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=davej@redhat.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.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.