From: Tony Lindgren <tony@atomide.com>
To: Franziska Naepelt <franziska.naepelt@googlemail.com>
Cc: linux-omap@vger.kernel.org, paul@pwsan.com,
linux@armlinux.org.uk, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Franziska Naepelt <franziska.naepelt@gmail.com>
Subject: Re: [PATCH] ARM: omap2: Fix checkpatch issues
Date: Fri, 2 Jun 2023 12:34:04 +0300 [thread overview]
Message-ID: <20230602093404.GQ14287@atomide.com> (raw)
In-Reply-To: <20230531170427.42199-1-franziska.naepelt@gmail.com>
* Franziska Naepelt <franziska.naepelt@googlemail.com> [230531 20:04]:
> The following checkpatch issues have been resolved:
>
> arch/arm/mach-omap2/omap-wakeupgen.c
> WARNING: Missing a blank line after declarations
>
> arch/arm/mach-omap2/omap_hwmod_3xxx_data.c
> ERROR: space prohibited before that ',' (ctx:WxE)
> WARNING: Use lore.kernel.org archive links when possible
>
> arch/arm/mach-omap2/omap_phy_internal.c
> WARNING: Block comments should align the * on each line
>
> arch/arm/mach-omap2/sdrc2xxx.c
> WARNING: It's generally not useful to have the filename in the file
>
> arch/arm/mach-omap2/ti81xx-restart.c
> ERROR: trailing statements should be on next line
Thanks applying into omap-for-v6.5/cleanup.
Tony
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Franziska Naepelt <franziska.naepelt@googlemail.com>
Cc: linux-omap@vger.kernel.org, paul@pwsan.com,
linux@armlinux.org.uk, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Franziska Naepelt <franziska.naepelt@gmail.com>
Subject: Re: [PATCH] ARM: omap2: Fix checkpatch issues
Date: Fri, 2 Jun 2023 12:34:04 +0300 [thread overview]
Message-ID: <20230602093404.GQ14287@atomide.com> (raw)
In-Reply-To: <20230531170427.42199-1-franziska.naepelt@gmail.com>
* Franziska Naepelt <franziska.naepelt@googlemail.com> [230531 20:04]:
> The following checkpatch issues have been resolved:
>
> arch/arm/mach-omap2/omap-wakeupgen.c
> WARNING: Missing a blank line after declarations
>
> arch/arm/mach-omap2/omap_hwmod_3xxx_data.c
> ERROR: space prohibited before that ',' (ctx:WxE)
> WARNING: Use lore.kernel.org archive links when possible
>
> arch/arm/mach-omap2/omap_phy_internal.c
> WARNING: Block comments should align the * on each line
>
> arch/arm/mach-omap2/sdrc2xxx.c
> WARNING: It's generally not useful to have the filename in the file
>
> arch/arm/mach-omap2/ti81xx-restart.c
> ERROR: trailing statements should be on next line
Thanks applying into omap-for-v6.5/cleanup.
Tony
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-06-02 9:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 17:04 [PATCH] ARM: omap2: Fix checkpatch issues Franziska Naepelt
2023-05-31 17:04 ` Franziska Naepelt
2023-06-02 9:34 ` Tony Lindgren [this message]
2023-06-02 9:34 ` Tony Lindgren
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=20230602093404.GQ14287@atomide.com \
--to=tony@atomide.com \
--cc=franziska.naepelt@gmail.com \
--cc=franziska.naepelt@googlemail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=paul@pwsan.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.