From: Rob Herring <robh@kernel.org>
To: Daire McNamara <daire.mcnamara@microchip.com>
Cc: linux-pci@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 1/3] PCI: Add vendor ID for Microsemi
Date: Mon, 18 Feb 2019 12:36:22 -0600 [thread overview]
Message-ID: <20190218183622.GA16980@bogus> (raw)
In-Reply-To: <20190215162424.564-2-daire.mcnamara@microchip.com>
On Fri, Feb 15, 2019 at 04:24:22PM +0000, Daire McNamara wrote:
> This patch adds a new PCI vendor ID for Microsemi.
A 'PCI vendor ID' is something else.
This patch and file have nothing to do with PCI.
>
> Signed-off-by: Daire McNamara <daire.mcnamara@microchip.com>
> ---
> Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt b/Documentation/devicetree/bindings/vendor-prefixes.txt
> index 4b1a2a8fcc16..d13f6e40dbf4 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.txt
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.txt
> @@ -238,6 +238,7 @@ micrel Micrel Inc.
> microchip Microchip Technology Inc.
> microcrystal Micro Crystal AG
> micron Micron Technology Inc.
> +microsemi Microsemi Corporation
> mikroe MikroElektronika d.o.o.
> minix MINIX Technology Ltd.
> miramems MiraMEMS Sensing Technology Co., Ltd.
> --
> 2.17.0
>
next prev parent reply other threads:[~2019-02-18 18:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 16:24 [PATCH v3 0/3] Add Microchip/Microsemi PolarFire SoC PCIe support Daire McNamara
2019-02-15 16:24 ` [PATCH v3 1/3] PCI: Add vendor ID for Microsemi Daire McNamara
2019-02-18 18:36 ` Rob Herring [this message]
2019-02-15 16:24 ` [PATCH v3 2/3] dt-bindings: PCI: microsemi: Add DT Bindings for Microsemi PCIe host controller Daire McNamara
2019-02-18 18:42 ` Rob Herring
2019-04-02 16:24 ` Lorenzo Pieralisi
2019-02-15 16:24 ` [PATCH v3 3/3] PCI: microsemi: Add host driver for Microsemi PCIe controller Daire McNamara
2019-02-16 8:04 ` Christoph Hellwig
2019-04-02 18:23 ` Lorenzo Pieralisi
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=20190218183622.GA16980@bogus \
--to=robh@kernel.org \
--cc=daire.mcnamara@microchip.com \
--cc=devicetree@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 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).