linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] libsysfs + namedev.c changes for naming
Date: Wed, 14 Jan 2004 00:32:20 +0000	[thread overview]
Message-ID: <20040114003220.GA8054@kroah.com> (raw)

On Tue, Jan 13, 2004 at 11:53:49PM -0000, Ananth  Narayan wrote:
> Hello Greg,
> 
> Here is a patch that applies on the earlier (_BIG_) patch; this solves the
> naming issue for me for both the normal and klibc builds. Basically, this
> patch adds a new sysfs_get_device_bus() call that can be used in cases where the sysfs part of the kernel hasn't got around creating the device
> link in the "bus" subsystem - reason why sysfs_device->bus shows up as 
> "unknown" rather than the actual bus name.
> 
> Tested for a USB storage device with a "LABEL" rule

Can you send me a big all-in-one patch that I can apply on top of the
013 release to test out?

thanks,

greg k-h


-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

             reply	other threads:[~2004-01-14  0:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-14  0:32 Greg KH [this message]
2004-01-14 22:53 ` Re: [PATCH] libsysfs + namedev.c changes for naming 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=20040114003220.GA8054@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-hotplug@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).