From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Stefan Assmann <sassmann@redhat.com>
Cc: linux-pci@vger.kernel.org, jeff@garzik.org,
linux-kernel@vger.kernel.org, rjw@sisk.pl, ddutile@redhat.com,
kaneshige.kenji@jp.fujitsu.com,
Stefan Assmann <sassmann@redhat.com>,
khc@pm.waw.pl
Subject: Re: [PATCH 1/2 v2] pci: change PCI nomenclature in drivers/pci/ (comment changes)
Date: Wed, 16 Dec 2009 11:45:17 -0800 [thread overview]
Message-ID: <20091216114517.4efe1eb2@jbarnes-piketon> (raw)
In-Reply-To: <20091203114923.24905.48449.sendpatchset@localhost.localdomain>
On Thu, 3 Dec 2009 06:49:24 -0500
Stefan Assmann <sassmann@redhat.com> 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
>
> Patch is limited to drivers/pci/ and changes concern comments only.
>
> Signed-off-by: Stefan Assmann <sassmann@redhat.com>
> ---
Applied these, thanks. The second one had a conflict since I had
previously applied a hotplug cleanup patch from you, but everything
else looked fine.
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2009-12-16 19:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 11:49 [PATCH 0/2 v2] pci: change PCI nomenclature according to PCI-SIG Stefan Assmann
2009-12-03 11:49 ` [PATCH 1/2 v2] pci: change PCI nomenclature in drivers/pci/ (comment changes) Stefan Assmann
2009-12-03 17:04 ` Stefan Assmann
2009-12-03 17:43 ` Jeff Garzik
2009-12-16 19:45 ` Jesse Barnes [this message]
2009-12-03 11:49 ` [PATCH 2/2 v2] pci: change PCI nomenclature in drivers/pci/ (non-comment changes) Stefan Assmann
2009-12-03 16:27 ` Andrew Patterson
2009-12-03 17:00 ` Stefan Assmann
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=20091216114517.4efe1eb2@jbarnes-piketon \
--to=jbarnes@virtuousgeek.org \
--cc=ddutile@redhat.com \
--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 \
--cc=rjw@sisk.pl \
--cc=sassmann@redhat.com \
/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
all inboxes | Powered by JetHome®