linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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:45:12 -0400	[thread overview]
Message-ID: <20030818164512.GF24693@gtf.org> (raw)
In-Reply-To: <200308181611.h7IGBEcW024487@hera.kernel.org>

On Mon, Aug 18, 2003 at 05:24:13AM +0000, Linux Kernel Mailing List wrote:
> --- a/arch/alpha/kernel/sys_marvel.c	Mon Aug 18 09:11:18 2003
> +++ b/arch/alpha/kernel/sys_marvel.c	Mon Aug 18 09:11:18 2003
> @@ -33,6 +33,13 @@
> +/* ??? Should probably be generic.  */
> +#ifdef CONFIG_PCI_NAMES
> +#define pci_pretty_name(x) ((x)->pretty_name)
> +#else
> +#define pci_pretty_name(x) ""
> +#endif
> +

> @@ -378,7 +385,7 @@
>  		       PCI_SLOT(dev->devfn), 
>  		       PCI_FUNC(dev->devfn),
>  		       hose->index,
> -		       dev->dev.name);
> +		       pci_pretty_name (dev));
>  		printk("  %d message(s) from 0x%04x\n", 

hmmm, I think a better fix can be had...  We store all that information.

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.

This assumes, of course, marvel_map_irq is called after pci_name() is
assigned a value...

	Jeff





===== arch/alpha/kernel/sys_marvel.c 1.7 vs edited =====
--- 1.7/arch/alpha/kernel/sys_marvel.c	Mon Aug 18 01:23:05 2003
+++ edited/arch/alpha/kernel/sys_marvel.c	Mon Aug 18 12:43:51 2003
@@ -33,13 +33,6 @@
 # error NR_IRQS < MARVEL_NR_IRQS !!!
 #endif
 
-/* ??? Should probably be generic.  */
-#ifdef CONFIG_PCI_NAMES
-#define pci_pretty_name(x) ((x)->pretty_name)
-#else
-#define pci_pretty_name(x) ""
-#endif
-
 \f
 /*
  * Interrupt handling.
@@ -380,12 +373,7 @@
 		irq += 0x80;			/* offset for lsi       */
 
 #if 1
-		printk("PCI:%d:%d:%d (hose %d) [%s] is using MSI\n",
-		       dev->bus->number, 
-		       PCI_SLOT(dev->devfn), 
-		       PCI_FUNC(dev->devfn),
-		       hose->index,
-		       pci_pretty_name (dev));
+		printk("PCI:%s is using MSI\n", pci_name (dev));
 		printk("  %d message(s) from 0x%04x\n", 
 		       1 << ((msg_ctl & PCI_MSI_FLAGS_QSIZE) >> 4),
 		       msg_dat);

       reply	other threads:[~2003-08-18 16:45 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 ` Jeff Garzik [this message]
2003-08-18 16:51   ` [ALPHA] Update for "name" out of struct device Jeff Garzik
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=20030818164512.GF24693@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).