linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Gary Bisson <bisson.gary@gmail.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, robh@kernel.org,
	krzk+dt@kernel.org
Subject: Re: [PATCH 1/5] dt-bindings: vendor-prefixes: Add Ezurio LLC
Date: Mon, 1 Dec 2025 09:59:55 +0100	[thread overview]
Message-ID: <aS1ZCy2G03zZLH6D@owl5> (raw)
In-Reply-To: <f9e30721-a636-41dc-93ab-ca960e0415ab@kernel.org>

Hi,

On Mon, Dec 01, 2025 at 09:50:07AM +0100, Krzysztof Kozlowski wrote:
> On 01/12/2025 09:41, Gary Bisson wrote:
> > Ezurio is the new name of Laird Connectivity after it acquired Boundary
> > Devices.
> > 
> > Signed-off-by: Gary Bisson <bisson.gary@gmail.com>
> > ---
> > Cc: robh@kernel.org
> > Cc: krzk+dt@kernel.org
> 
> Why only two of us? Please don't work on old kernels, some ancient code.
> 
> Please use scripts/get_maintainers.pl to get a list of necessary people
> and lists to CC (and consider --no-git-fallback argument, so you will
> not CC people just because they made one commit years ago). It might
> happen, that command when run on an older kernel, gives you outdated
> entries. Therefore please be sure you base your patches on recent Linux
> kernel.

Actually I'm using master so the get_maintainer.pl output is fine, just
wasn't using b4 and addding the CC myself, will resend with b4 and will
update the patches per your review.

> Tools like b4 or scripts/get_maintainer.pl provide you proper list of
> people, so fix your workflow. Tools might also fail if you work on some
> ancient tree (don't, instead use mainline) or work on fork of kernel
> (don't, instead use mainline). Just use b4 and everything should be
> fine, although remember about `b4 prep --auto-to-cc` if you added new
> patches to the patchset.
> 
> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>

Thanks for the quick review of the series.

Regards,
Gary


  reply	other threads:[~2025-12-01  9:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-01  8:41 [PATCH 0/5] Add support for Ezurio MediaTek platforms Gary Bisson
2025-12-01  8:41 ` [PATCH 1/5] dt-bindings: vendor-prefixes: Add Ezurio LLC Gary Bisson
2025-12-01  8:50   ` Krzysztof Kozlowski
2025-12-01  8:59     ` Gary Bisson [this message]
2025-12-01  9:33   ` Rob Herring (Arm)
2025-12-01 10:04     ` Gary Bisson
2025-12-01 10:10       ` Krzysztof Kozlowski
2025-12-01  8:41 ` [PATCH 2/5] dt-bindings: arm: mediatek: Add ezurio,mt8370-tungsten-smarc Gary Bisson
2025-12-01  8:51   ` Krzysztof Kozlowski
2025-12-01  9:33   ` Rob Herring (Arm)
2025-12-01  8:41 ` [PATCH 3/5] dt-bindings: arm: mediatek: Add ezurio,mt8390-tungsten-smarc Gary Bisson
2025-12-01  9:33   ` Rob Herring (Arm)
2025-12-01  8:41 ` [PATCH 4/5] arm64: dts: mediatek: add device tree for Tungsten 510 board Gary Bisson
2025-12-01  8:53   ` Krzysztof Kozlowski
2025-12-01  8:41 ` [PATCH 5/5] arm64: dts: mediatek: add device tree for Tungsten 700 board Gary Bisson

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=aS1ZCy2G03zZLH6D@owl5 \
    --to=bisson.gary@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --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;
as well as URLs for NNTP newsgroup(s).