From: Greg KH <greg@kroah.com>
To: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI vendor and device strings in sysfs
Date: Thu, 17 Jul 2003 19:35:52 -0700 [thread overview]
Message-ID: <20030718023552.GA5926@kroah.com> (raw)
In-Reply-To: <20030717101123.GA6069@in.ibm.com>
On Thu, Jul 17, 2003 at 03:41:24PM +0530, Ananth N Mavinakayanahalli wrote:
> Hi,
>
> Here is a patch against 2.6.0-test1 to display PCI vendor and
> device strings in sysfs.
>
> At present, the PCI "name" attribute has a length restriction
> (DEVICE_NAME_SIZE) within which it tries to accomodate the vendor
> and device strings, leading to, in most cases, truncation of one
> or both strings.
>
> This patch alleviates the issue by creating the vendor_name and
> device_name attributes for PCI devices.
I agree with Pat, this should be done in userspace.
We should really just get rid of the dev->name file all together to keep
people from relying on it :)
thanks,
greg k-h
prev parent reply other threads:[~2003-07-18 2:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-17 10:11 [PATCH] PCI vendor and device strings in sysfs Ananth N Mavinakayanahalli
2003-07-17 14:55 ` Patrick Mochel
2003-07-18 2:35 ` 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=20030718023552.GA5926@kroah.com \
--to=greg@kroah.com \
--cc=ananth@in.ibm.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.