devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Brian Norris <briannorris@chromium.org>
Cc: Frank Li <Frank.Li@nxp.com>,
	 "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	 Jakub Kicinski <kuba@kernel.org>,
	Paolo Abeni <pabeni@redhat.com>,  Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	 Conor Dooley <conor+dt@kernel.org>,
	 "open list:NETWORKING DRIVERS (WIRELESS)"
	<linux-wireless@vger.kernel.org>,
	 "open list:NETWORKING DRIVERS" <netdev@vger.kernel.org>,
	 "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>,
	 open list <linux-kernel@vger.kernel.org>,
	 imx@lists.linux.dev
Subject: Re: [PATCH v2 1/1] dt-bindings: net: wireless: convert marvel-8xxx.txt to yaml format
Date: Tue, 20 Aug 2024 12:17:51 +0300	[thread overview]
Message-ID: <87seuzwo1s.fsf@kernel.org> (raw)
In-Reply-To: <ZsPccHaCMRgbNk4L@google.com> (Brian Norris's message of "Mon, 19 Aug 2024 16:59:44 -0700")

Brian Norris <briannorris@chromium.org> writes:

> Hi Frank,
>
> On Fri, Aug 16, 2024 at 01:12:01PM -0400, Frank Li wrote:
>> Convert binding doc marvel-8xxx.txt to yaml format.
>> Additional change:
>> - Remove marvell,caldata_00_txpwrlimit_2g_cfg_set in example.
>> - Remove mmc related property in example.
>> - Add wakeup-source property.
>> - Remove vmmc-supply and mmc-pwrseq.
>> 
>> Fix below warning:
>> arch/arm64/boot/dts/freescale/imx8mp-beacon-kit.dtb: /soc@0/bus@30800000/mmc@30b40000/wifi@1:
>> failed to match any schema with compatible: ['marvell,sd8997']
>> 
>> Signed-off-by: Frank Li <Frank.Li@nxp.com>
>> ---
>> Change from v1 to v2
>> - Add Brian Norris <briannorris@chromium.org as maintainer
>> - Remove vmmc-supply and mmc-pwrseq
>> - Add wakeup-source
>> - rename to marvell,sd8787.yaml by using one compatible string, suggestted
>> by conor dooley at other binding doc convert review
>> ---
>>  .../bindings/net/wireless/marvell,sd8787.yaml | 93 +++++++++++++++++++
>>  .../bindings/net/wireless/marvell-8xxx.txt    | 70 --------------
>>  2 files changed, 93 insertions(+), 70 deletions(-)
>>  create mode 100644 Documentation/devicetree/bindings/net/wireless/marvell,sd8787.yaml
>>  delete mode 100644 Documentation/devicetree/bindings/net/wireless/marvell-8xxx.txt
>> 
>> diff --git a/Documentation/devicetree/bindings/net/wireless/marvell,sd8787.yaml b/Documentation/devicetree/bindings/net/wireless/marvell,sd8787.yaml
>> new file mode 100644
>> index 0000000000000..c6647672b7b1e
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/net/wireless/marvell,sd8787.yaml
>> @@ -0,0 +1,93 @@
>
>> +  marvell,caldata-txpwrlimit-5g-sub0:
>> +    $ref: /schemas/types.yaml#/definitions/uint8-array
>> +    description: Calibration data for sub-band 0 in the 5GHz band..
>
> You have an extra period in this line.
>
>> +  marvell,caldata-txpwrlimit-5g-sub1:
>> +    $ref: /schemas/types.yaml#/definitions/uint8-array
>> +    description: Calibration data for sub-band 1 in the 5GHz band..
>
> Same.
>
>> +    maxItems: 688
>> +
>> +  marvell,caldata-txpwrlimit-5g-sub2:
>> +    $ref: /schemas/types.yaml#/definitions/uint8-array
>> +    description: Calibration data for sub-band 2 in the 5GHz band..
>
> Same.
>
> Otherwise, this looks good to me, so feel free to carry my:
>
> Acked-by: Brian Norris <briannorris@chromium.org>
>
> (Sometimes Kalle will make trivial fixes like this when applying. I'm
> not sure if that means you should send v3 anyway, or see if he'll apply
> this on his own soon enough.)

For wireless-next patches I can easily edit commit messages but not the
actual patch, so please send v3.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

      reply	other threads:[~2024-08-20  9:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-16 17:12 [PATCH v2 1/1] dt-bindings: net: wireless: convert marvel-8xxx.txt to yaml format Frank Li
2024-08-18 16:07 ` Rob Herring (Arm)
2024-08-19 23:59 ` Brian Norris
2024-08-20  9:17   ` Kalle Valo [this message]

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=87seuzwo1s.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=Frank.Li@nxp.com \
    --cc=briannorris@chromium.org \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=imx@lists.linux.dev \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).