From: Jeff Garzik <jgarzik@pobox.com>
To: rth@twiddle.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ALPHA] Update for "name" out of struct device.
Date: Mon, 18 Aug 2003 12:51:09 -0400 [thread overview]
Message-ID: <20030818165109.GG24693@gtf.org> (raw)
In-Reply-To: <20030818164512.GF24693@gtf.org>
On Mon, Aug 18, 2003 at 12:45:12PM -0400, Jeff Garzik wrote:
> What do you think about the following patch? It follows the style of
> other PCI core messages, and prints out the same information as before.
...except for the pretty name, of course.
But IMO we need to stop drivers and core from printing out pretty-name
at all, which is another reason for my patch. Having name information
like this in the kernel, overall, is a waste, IMO. _Especially_ when
that information is conditional. We should be consistent with what we
print out, to reduce user confusion.
Jeff
next prev parent reply other threads:[~2003-08-18 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200308181611.h7IGBEcW024487@hera.kernel.org>
2003-08-18 16:45 ` [ALPHA] Update for "name" out of struct device Jeff Garzik
2003-08-18 16:51 ` Jeff Garzik [this message]
2003-08-18 20:32 ` 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=20030818165109.GG24693@gtf.org \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rth@twiddle.net \
/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).