Devicetree
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jacobe Zang <jacobe.zang@wesion.com>,
	kvalo@kernel.org, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org
Cc: nick@khadas.com, arend@broadcom.com,
	linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] dt-bindings: net: wireless: BCM4329 binding: add pci14e4,449d
Date: Mon, 17 Jun 2024 08:18:53 +0200	[thread overview]
Message-ID: <bbd04c56-451a-4a5f-938c-2ce4ccec7253@kernel.org> (raw)
In-Reply-To: <20240617024341.3106240-1-jacobe.zang@wesion.com>

On 17/06/2024 04:43, Jacobe Zang wrote:
> It's a Broadcom Wi-Fi module connected via the PCIe interface and also
> add prefix in vendor-prefix.yaml

You do not add prefix here. Drop unrelated parts of commit msg.

> 
> Link:https://lore.kernel.org/linux-devicetree/20240617023517.3104427-1-jacobe.zang@wesion.com/T/#u

Link also does not seem to be really relevant to the commit. No point to
keep it in the git log. You can always provide additional information in
the changelog section (---).


> Signed-off-by: Jacobe Zang <jacobe.zang@wesion.com>
> ---
>  .../devicetree/bindings/net/wireless/brcm,bcm4329-fmac.yaml      | 1 +
>  1 file changed, 1 insertion(+)


Best regards,
Krzysztof


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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-17  2:43 [PATCH v1] dt-bindings: net: wireless: BCM4329 binding: add pci14e4,449d Jacobe Zang
2024-06-17  6:18 ` Krzysztof Kozlowski [this message]
2024-06-17  6:30   ` Jacobe Zang
2024-06-18 11:09 ` Arend Van Spriel
2024-06-18 14:47   ` Sebastian Reichel

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=bbd04c56-451a-4a5f-938c-2ce4ccec7253@kernel.org \
    --to=krzk@kernel.org \
    --cc=arend@broadcom.com \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=jacobe.zang@wesion.com \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nick@khadas.com \
    --cc=pabeni@redhat.com \
    --cc=robh@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