From: Kay Sievers <kay.sievers@vrfy.org>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Greg KH <greg@kroah.com>, Mark Lord <lkml@rtr.ca>,
NeilBrown <neilb@suse.de>, SL Baur <steve@xemacs.org>,
Tejun Heo <htejun@gmail.com>, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH try2] sysfs: add /sys/dev/{char,block} to lookupsysfs path by major:minor
Date: Sat, 19 Apr 2008 08:16:58 +0200 [thread overview]
Message-ID: <1208585818.8589.36.camel@lov.site> (raw)
In-Reply-To: <1208565705.5083.27.camel@dwillia2-linux.ch.intel.com>
On Fri, 2008-04-18 at 17:41 -0700, Dan Williams wrote:
> On Fri, 2008-04-18 at 13:53 -0700, Kay Sievers wrote:
> > On Fri, 2008-04-18 at 12:33 -0700, Dan Williams wrote:
> > Also:
> > class_create(THIS_MODULE, "usb_device");
> > in:
> > drivers/usb/core/devio.c
> > should probably clear the dev_kobj after registration, and we can get
> > rid of the "parent has the same dev_t" logic?
>
> Greg had suspicions that there might be more cases like
> usb_classdev_class, so I added a dev_warn() to help debug those.
Yeah, it's Linux, you never know. :) But there are no currently known
other subsystem doing this. It is perfectly valid scenario though, to
have that, if someone comes up with a better idea as some current stuff
is doing it, and we need to deprecate something, and have duplicated
dev_t entries in sysfs for a while.
> I don't mind taking your word for it that there are no more such cases,
> but maybe the warning should stay in for a few -rc releases?
I think, we can remove that, as it will print a warning for the
"duplicate entry" anyway.
Looks all fine now from my point of view.
Thanks,
Kay
prev parent reply other threads:[~2008-04-19 6:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1208547223.5083.17.camel@dwillia2-linux.ch.intel.com>
2008-04-18 20:53 ` [RFC PATCH try2] sysfs: add /sys/dev/{char,block} to lookup sysfs path by major:minor Kay Sievers
[not found] ` <1208565705.5083.27.camel@dwillia2-linux.ch.intel.com>
2008-04-19 6:16 ` Kay Sievers [this message]
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=1208585818.8589.36.camel@lov.site \
--to=kay.sievers@vrfy.org \
--cc=dan.j.williams@intel.com \
--cc=greg@kroah.com \
--cc=hpa@zytor.com \
--cc=htejun@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=neilb@suse.de \
--cc=steve@xemacs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox