mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jacobe Zang <jacobe.zang@wesion.com>,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org
Cc: nick@khadas.com, heiko.stuebner@cherry.de,
	neil.armstrong@linaro.org, macromorgan@hotmail.com,
	sre@kernel.org, hvilleneuve@dimonoff.com, andre.przywara@arm.com,
	michael.riesch@wolfvision.net, linus.walleij@linaro.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] dt-bindings: vendor-prefixes: Add a pci14e4 entry
Date: Mon, 17 Jun 2024 08:23:11 +0200	[thread overview]
Message-ID: <b859c506-9910-43a6-923c-2a9ee26c4f19@kernel.org> (raw)
In-Reply-To: <20240617023517.3104427-1-jacobe.zang@wesion.com>

On 17/06/2024 04:35, Jacobe Zang wrote:
> Add Broadcom pci14e4 prefix for PCIe Wi-Fi module in dts.
> 
> Signed-off-by: Jacobe Zang <jacobe.zang@wesion.com>
> ---
>  Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> index fbf47f0bacf1a..d0db6df57bfe5 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> @@ -1112,6 +1112,8 @@ patternProperties:
>      description: Parade Technologies Inc.
>    "^parallax,.*":
>      description: Parallax Inc.
> +  "^pci14e4,.*":
> +    description: Broadcom Corporation

I think this is not needed. We do not document PCI or USB prefixes.


Best regards,
Krzysztof


  reply	other threads:[~2024-06-17  6:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-17  2:35 Jacobe Zang
2024-06-17  6:23 ` Krzysztof Kozlowski [this message]
2024-06-17  6:34   ` Jacobe Zang

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=b859c506-9910-43a6-923c-2a9ee26c4f19@kernel.org \
    --to=krzk@kernel.org \
    --cc=andre.przywara@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko.stuebner@cherry.de \
    --cc=hvilleneuve@dimonoff.com \
    --cc=jacobe.zang@wesion.com \
    --cc=krzk+dt@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macromorgan@hotmail.com \
    --cc=michael.riesch@wolfvision.net \
    --cc=neil.armstrong@linaro.org \
    --cc=nick@khadas.com \
    --cc=robh@kernel.org \
    --cc=sre@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

all inboxes | Powered by JetHome®