mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mirsad Todorovac <mtodorovac69@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Peter Rosin <peda@axentia.se>
Subject: [PROBLEM linux-next] drivers/mux/adg792a.c:134:34: error: ‘adg792a_of_match’ defined but not used [-Werror=unused-const-variable=]
Date: Tue, 9 Jul 2024 23:20:34 +0200	[thread overview]
Message-ID: <d1145d32-4b77-479d-bc66-0bb8694a6923@gmail.com> (raw)

Dear all,

On the linux-next vanilla next-20240709 tree, I have attempted the seed KCONFIG_SEED=0xEE7AB52F
which was known from before to trigger various errors in compile and build process.

Though this might seem as contributing to channel noise, Linux refuses to build this config,
treating warnings as errors, using this build line:

$ time nice make W=1 -k -j 36 |& tee ../err-next-20230709-01a.log; date

As I know that the Chief Penguin doesn't like warnings, but I am also aware that there are plenty
left, there seems to be more tedious work ahead to make the compilers happy.

The compiler output is:

drivers/mux/adg792a.c:134:34: error: ‘adg792a_of_match’ defined but not used [-Werror=unused-const-variable=]
  134 | static const struct of_device_id adg792a_of_match[] = {
      |                                  ^~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors

The offending lines are:

drivers/mux/adg792a.c:134
134 static const struct of_device_id adg792a_of_match[] = {
135         { .compatible = "adi,adg792a", },
136         { .compatible = "adi,adg792g", },
137         { }
138 };
139 MODULE_DEVICE_TABLE(of, adg792a_of_match);

Hope this helps.

Best regards,
Mirsad Todorovac

             reply	other threads:[~2024-07-09 21:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-09 21:20 Mirsad Todorovac [this message]
2024-07-09 21:28 Mirsad Todorovac

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=d1145d32-4b77-479d-bc66-0bb8694a6923@gmail.com \
    --to=mtodorovac69@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peda@axentia.se \
    /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

all inboxes | Powered by JetHome®