From: Greg KH <greg@kroah.com>
To: Dave Airlie <airlied@gmail.com>
Cc: airlied@linux.ie, Kay Sievers <kay.sievers@vrfy.org>,
dri-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
linux-hotplug-devel@lists.sourceforge.net
Subject: Re: [PATCH] cleanup of the drm sysfs code.
Date: Mon, 23 Jan 2006 20:58:49 -0800 [thread overview]
Message-ID: <20060124045849.GB22434@kroah.com> (raw)
In-Reply-To: <21d7e9970601211403g44ce4845yd03f12f64142ef36@mail.gmail.com>
On Sun, Jan 22, 2006 at 11:03:16AM +1300, Dave Airlie wrote:
> > Kay pointed out today that the drm code creates a "dev" file in sysfs,
> > yet doesn't tell the driver core about it. Normally this would be just
> > fine, as you are exporting the value in the proper style, but now there
> > are programs that are only watching the hotplug/uevent netlink messages
> > and not reading directly from sysfs to get this kind of information.
> > The patch below is a cleanup of the drm sysfs code, as much of the same
> > functionality that you want is already present in the driver core, so it
> > is not good to duplicate it.
>
> Greg it looks fine to me, I'm LCA'ing at the moment, so if you can
> push it via your tree I'm fine with it, if you can let it sit in an
> -mm picked up tree for a bit I'd appreciate it, but we don't do much
> with sysfs anyways other than create the dev..
Ok, thanks. I'll get it into the next few -mm releases, and as Linus is
also with you at linux.conf.au, I don't really worry about getting the
patch to him until he returns.
> I'm going to hopefully get around to the drm/fb merge layer in the
> next month so I'd prefer to start from a clean state..
Sounds good to me, I'll probably have the time to help out with this if
you want...
thanks,
greg k-h
prev parent reply other threads:[~2006-01-24 4:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-20 23:33 [PATCH] cleanup of the drm sysfs code Greg KH
2006-01-21 22:03 ` Dave Airlie
2006-01-24 4:58 ` Greg KH [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=20060124045849.GB22434@kroah.com \
--to=greg@kroah.com \
--cc=airlied@gmail.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.sourceforge.net \
--cc=kay.sievers@vrfy.org \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).