From: Tejun Heo <htejun@gmail.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Florin Iucha <florin@iucha.net>,
USB development list <linux-usb-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Greg KH <gregkh@suse.de>,
Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
"Randy. Dunlap" <rdunlap@xenotime.net>
Subject: Re: [linux-usb-devel] USB-related oops in sysfs with linux v2.6.23-rc3-50-g28e8351
Date: Thu, 16 Aug 2007 00:30:03 +0900 [thread overview]
Message-ID: <46C31BFB.6040702@gmail.com> (raw)
In-Reply-To: <20070815172133.4f2eeda8@gondolin.boeblingen.de.ibm.com>
Cornelia Huck wrote:
> On Wed, 15 Aug 2007 23:54:43 +0900,
> Tejun Heo <htejun@gmail.com> wrote:
>
>> Alan Stern wrote:
>>> I think we can simply remove the error message. There's no obvious
>>> reason why sysfs_remove_bin_file() should complain about attempts to
>>> remove a nonexistent file; sysfs_remove_file() doesn't.
>>>
>>> This patch will get rid of the annoying error messages. It won't do
>>> anything about your keyboard's tendency to spontaneously stop working,
>>> alas.
>> Agreed but I think sysfs_remove_bin_file() should relay the return value
>> from sysfs_has_and_remove() to the caller.
>
> Three comments:
>
> - Randy made sysfs_remove_bin_file() return void in commit
> 995982ca79d9262869513948ec7c540f32035491.
>
> - For symmetry reasons, sysfs_remove_file() should then also pass the
> return value on.
>
> - I'm not sure who wants to care whether they removed an existing or
> non-existing file. But maybe I'm just unimaginative.
Hmmm... Well, failure information is lost there, so I was a bit worried.
It probably doesn't really matter and can be easily changed later if
needed. If sysfs_remove_file() returns void, I have no objection.
Thanks.
--
tejun
next prev parent reply other threads:[~2007-08-15 15:30 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-15 13:31 USB-related oops in sysfs with linux v2.6.23-rc3-50-g28e8351 Florin Iucha
2007-08-15 14:38 ` [linux-usb-devel] " Alan Stern
2007-08-15 14:50 ` Florin Iucha
2007-08-15 15:24 ` Alan Stern
2007-08-15 14:54 ` Tejun Heo
2007-08-15 15:21 ` Cornelia Huck
2007-08-15 15:30 ` Tejun Heo [this message]
2007-08-15 15:33 ` Alan Stern
2007-08-15 14:49 ` Jiri Kosina
2007-08-15 14:53 ` Florin Iucha
2007-08-15 14:58 ` Jiri Kosina
2007-08-21 11:51 ` Florin Iucha
2007-08-21 12:04 ` Jiri Kosina
2007-08-21 12:28 ` Florin Iucha
2007-08-21 14:51 ` Alan Stern
2007-08-21 12:06 ` Oliver Neukum
2007-08-21 12:09 ` Jiri Kosina
2007-08-21 12:19 ` Oliver Neukum
2007-08-21 12:57 ` Florin Iucha
2007-08-21 13:05 ` Jiri Kosina
2007-08-21 13:17 ` Florin Iucha
2007-08-21 13:27 ` Florin Iucha
2007-08-21 13:42 ` Jiri Kosina
2007-08-22 13:22 ` Florin Iucha
2007-08-23 12:52 ` NFS woes again Was: " Florin Iucha
2007-08-23 17:14 ` Bret Towe
2007-08-23 17:36 ` Florin Iucha
2007-08-27 13:17 ` Trond Myklebust
2007-08-28 1:19 ` Bret Towe
2007-08-28 1:35 ` NFS woes again Florin Iucha
2007-08-28 13:28 ` Trond Myklebust
2007-08-29 3:27 ` Florin Iucha
2007-08-29 5:52 ` Bret Towe
2007-08-30 22:18 ` Bret Towe
2007-08-30 23:14 ` Florin Iucha
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=46C31BFB.6040702@gmail.com \
--to=htejun@gmail.com \
--cc=cornelia.huck@de.ibm.com \
--cc=florin@iucha.net \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=rdunlap@xenotime.net \
--cc=stern@rowland.harvard.edu \
/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.