Linux M68K Architecture development
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@linux-m68k.org>
To: Krzysztof Kozlowski <krzk@kernel.org>, linux-m68k@lists.linux-m68k.org
Subject: Re: [PATCH 03/13] net: fec: add device tree support for ColdFire FEC
Date: Wed, 19 Feb 2025 23:25:22 +1000	[thread overview]
Message-ID: <611a4c02-5200-410b-98c0-a4c586ba67bd@linux-m68k.org> (raw)
In-Reply-To: <624f666f-6b97-4afe-821a-8fbc57a408c4@kernel.org>


On 19/2/25 17:05, Krzysztof Kozlowski wrote:
> On 18/02/2025 13:46, Greg Ungerer wrote:
>> The FEC hardware module used in most Freescale ColdFire SoC parts is a
>> simpler version of that used on the iMX family of parts. Add a devicetree
>> compatible entry they can use.
>>
>> Signed-off-by: Greg Ungerer <gerg@linux-m68k.org>
>> ---
>>   Documentation/devicetree/bindings/net/fsl,fec.yaml | 1 +
> 
> Please run scripts/checkpatch.pl and fix reported warnings. After that,
> run also `scripts/checkpatch.pl --strict` and (probably) fix more

I did. I chose to ignore the documentation and frivolous formatting
warnings for now. See cover letter for reasoning.

Regards
Greg


> warnings. Some warnings can be ignored, especially from --strict run,
> but the code here looks like it needs a fix. Feel free to get in touch
> if the warning is not clear.
> 
> 
> <form letter>
> Please use scripts/get_maintainers.pl to get a list of necessary people
> and lists to CC. 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.
> 
> 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.
> 
> You missed at least devicetree list (maybe more), so this won't be
> tested by automated tooling. Performing review on untested code might be
> a waste of time.
> 
> Please kindly resend and include all necessary To/Cc entries.
> </form letter>
> 
> Best regards,
> Krzysztof


  reply	other threads:[~2025-02-19 13:25 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-18 12:46 [PATCH 00/13] m68k: coldfire: proof-of-concept devicetree Greg Ungerer
2025-02-18 12:46 ` [PATCH 01/13] serial: mcf: convert to use proper platform resources Greg Ungerer
2025-02-18 12:46 ` [PATCH 02/13] serial: mcf: add devicetree support Greg Ungerer
2025-02-18 12:46 ` [PATCH 03/13] net: fec: add device tree support for ColdFire FEC Greg Ungerer
2025-02-19  7:05   ` Krzysztof Kozlowski
2025-02-19 13:25     ` Greg Ungerer [this message]
2025-02-18 12:46 ` [PATCH 04/13] m68k: coldfire: enable common clock framework Greg Ungerer
2025-02-18 12:46 ` [PATCH 05/13] m68k: coldfire: support devicetree binding for intc-simr Greg Ungerer
2025-02-18 12:46 ` [PATCH 06/13] m68k: coldfire: support devicetree binding for intc controller Greg Ungerer
2025-02-18 12:46 ` [PATCH 07/13] m68k: coldfire: support devicetree binding for intc-2 controller Greg Ungerer
2025-02-18 12:46 ` [PATCH 08/13] m68k: coldfire: add devicetree for mcf5208-evb platform Greg Ungerer
2025-02-18 12:46 ` [PATCH 09/13] m68k: coldfire: add devicetree for mcf5475-evb platform Greg Ungerer
2025-02-19  7:06   ` Krzysztof Kozlowski
2025-02-19  8:23     ` Greg Ungerer
2025-02-19  8:26       ` Krzysztof Kozlowski
2025-02-19 21:58         ` Greg Ungerer
2025-02-18 12:46 ` [PATCH 10/13] m68k: implement an embedded devicetree for nonmmu Greg Ungerer
2025-02-20 14:06   ` Geert Uytterhoeven
2025-02-23 14:25     ` Greg Ungerer
2025-02-18 12:46 ` [PATCH 11/13] m68k: implement an embedded devicetree for mm targets Greg Ungerer
2025-02-18 12:46 ` [PATCH 12/13] m68k: coldfire: disable platform device tree entries Greg Ungerer
2025-02-18 12:46 ` [PATCH 13/13] m68k: coldfire: enable devicetree use Greg Ungerer

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=611a4c02-5200-410b-98c0-a4c586ba67bd@linux-m68k.org \
    --to=gerg@linux-m68k.org \
    --cc=krzk@kernel.org \
    --cc=linux-m68k@lists.linux-m68k.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