All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Assmann <sassmann@redhat.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-pci@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	Krzysztof Halasa <khc@pm.waw.pl>, Don Dutile <ddutile@redhat.com>,
	kaneshige.kenji@jp.fujitsu.com
Subject: Re: [PATCH] change PCI nomenclature according to PCI-SIG
Date: Sun, 29 Nov 2009 10:09:08 +0100	[thread overview]
Message-ID: <4B123A34.5090509@redhat.com> (raw)
In-Reply-To: <4B111ADC.9020800@garzik.org>

On 28.11.2009 13:43, Jeff Garzik wrote:
> On 11/28/2009 06:54 AM, Stefan Assmann wrote:
>> From: Stefan Assmann<sassmann@redhat.com>
>>
>> Changing occurrences of variants of PCI-X and PCIe to the PCI-SIG
>> terms listed in the "Trademark and Logo Usage Guidelines".
>> http://www.pcisig.com/developers/procedures/logos/Trademark_and_Logo_Usage_Guidelines_updated_112206.pdf
>>
>> Additionally some renames of Gb/s to GT/s where appropriate, concerns
>> PCIe.
>>
>> This is a followup to the discussion at:
>> http://lkml.org/lkml/2009/10/14/107
>> Patch is based on 2.6.32-rc8.
>>
>> Signed-off-by: Stefan Assmann<sassmann@redhat.com>
> 
> NAK, this clearly introduces bugs and changes sysfs output (ABI).
> 
> Typically this type of change is pointless churn that creates far more
> problems than it "solves."

Hi Jeff,

I see you point in not liking this kind of change. What kind of cleanup
would be ok in your opinion?

  Stefan
--
Stefan Assmann         | Red Hat GmbH
Software Engineer      | Otto-Hahn-Strasse 20, 85609 Dornach
                       | HR: Amtsgericht Muenchen HRB 153243
                       | GF: Brendan Lane, Charlie Peters,
sassmann at redhat.com |     Michael Cunningham, Charles Cachera

  reply	other threads:[~2009-11-29  9:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-28 11:54 [PATCH] change PCI nomenclature according to PCI-SIG Stefan Assmann
2009-11-28 12:43 ` Jeff Garzik
2009-11-29  9:09   ` Stefan Assmann [this message]
2009-11-29 12:54     ` Jeff Garzik
2009-11-29 15:12       ` Rafael J. Wysocki
2009-11-29 21:09       ` Krzysztof Halasa
2009-11-30  8:57       ` Stefan Assmann
2009-11-30 16:11       ` Jesse Barnes
2009-11-28 13:18 ` Krzysztof Halasa

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=4B123A34.5090509@redhat.com \
    --to=sassmann@redhat.com \
    --cc=ddutile@redhat.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=jeff@garzik.org \
    --cc=kaneshige.kenji@jp.fujitsu.com \
    --cc=khc@pm.waw.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@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.