From: kernel test robot <lkp@intel.com>
To: "Martin Povišer" <povik+lin@cutebit.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [asahilinux:sound/speaker-safety 146/206] checkpatch: WARNING: Missing a blank line after declarations
Date: Mon, 16 Oct 2023 09:25:32 +0800 [thread overview]
Message-ID: <202310160928.WFXPCAsk-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 795 bytes --]
tree: https://github.com/AsahiLinux/linux sound/speaker-safety
head: c4c1ca0ec7d6b3dcce7304ea88eaaad52f090d90
commit: ae723e076e0a0e0b091931365ef94785e10cc7d1 [146/206] ASoC: apple: mca: Support FEs being clock consumers
reproduce:
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202310160928.WFXPCAsk-lkp@intel.com/
# many are suggestions rather than must-fix
WARNING:LINE_SPACING: Missing a blank line after declarations
#95: FILE: sound/soc/apple/mca.c:392:
+ int port = mca_fe_get_port(substream);
+ writel_relaxed(port + 6 + 1,
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
[-- Attachment #2: reproduce --]
[-- Type: text/plain, Size: 101 bytes --]
reproduce:
scripts/checkpatch.pl 0001-ASoC-apple-mca-Support-FEs-being-clock-consumers.patch
next reply other threads:[~2023-10-16 1:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 1:25 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-16 0:41 [asahilinux:sound/speaker-safety 146/206] checkpatch: WARNING: Missing a blank line after declarations kernel test robot
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=202310160928.WFXPCAsk-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=povik+lin@cutebit.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 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.