public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Matthew Wilcox <willy@debian.org>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	linux-kernel@vger.kernel.org, mochel@osdl.org
Subject: Re: [PATCH] eliminate pci_dev name
Date: Thu, 14 Nov 2002 13:28:13 -0500	[thread overview]
Message-ID: <3DD3EB3D.8050606@pobox.com> (raw)
In-Reply-To: <20021114171017.B30392@parcelfarce.linux.theplanet.co.uk>

Matthew Wilcox wrote:

> diff -urpNX dontdiff linux-2.5.47/include/linux/pci.h 
> linux-2.5.47-willy/include/linux/pci.h
> --- linux-2.5.47/include/linux/pci.h	2002-11-14 10:52:17.000000000 -0500
> +++ linux-2.5.47-willy/include/linux/pci.h	2002-11-14 
> 11:43:40.000000000 -0500
> @@ -371,7 +371,6 @@ struct pci_dev {
>  	struct resource dma_resource[DEVICE_COUNT_DMA];
>  	struct resource irq_resource[DEVICE_COUNT_IRQ];
>
> -	char		name[90];	/* device name */
>  	char		slot_name[8];	/* slot name */
>  	int		active;		/* ISAPnP: device is active */
>  	int		ro;		/* ISAPnP: read only */
>


Patch looks pretty good to me... seems like the obvious (and useful) 
cleanup.

You should increase DEVICE_NAME_SIZE in include/linux/device.h from 80 
to 90, though.  I assume you don't want to take the other option, which 
is to audit every use and all the id strings to make sure they're short 
enough.  In fact, IIRC, device name increased in size due to some really 
long PCI names, so I think '90' will wind up the preferred value in any 
case.

	Jeff




  reply	other threads:[~2002-11-14 18:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-14 17:10 [PATCH] eliminate pci_dev name Matthew Wilcox
2002-11-14 18:28 ` Jeff Garzik [this message]
2002-11-14 18:34   ` Matthew Wilcox
2002-11-14 18:36   ` Linus Torvalds
2002-11-14 18:44     ` Matthew Wilcox
2002-11-14 19:22       ` Linus Torvalds
2002-11-14 20:44       ` Ingo Oeser
2002-11-16 23:47     ` Matthew Wilcox
2002-11-14 19:10   ` Jeff Garzik

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=3DD3EB3D.8050606@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@osdl.org \
    --cc=torvalds@transmeta.com \
    --cc=willy@debian.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