From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: Re: drivers/mux/adg792a.c:134:34: warning: 'adg792a_of_match' defined but not used
Date: Sat, 6 Jan 2024 17:04:03 +0200 [thread overview]
Message-ID: <ZZlr48NanPRkmkgl@smile.fi.intel.com> (raw)
In-Reply-To: <202312290237.ChqMrE6k-lkp@intel.com>
On Fri, Dec 29, 2023 at 02:46:30AM +0800, kernel test robot wrote:
> Hi Andy,
...
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202312290237.ChqMrE6k-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> >> drivers/mux/adg792a.c:134:34: warning: 'adg792a_of_match' defined but not used [-Wunused-const-variable=]
> 134 | static const struct of_device_id adg792a_of_match[] = {
> | ^~~~~~~~~~~~~~~~
of_match_ptr() should be dropped.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-01-06 15:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-28 18:46 drivers/mux/adg792a.c:134:34: warning: 'adg792a_of_match' defined but not used kernel test robot
2024-01-06 15:04 ` Andy Shevchenko [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-13 5:08 kernel test robot
2025-01-06 8:54 kernel test robot
2024-01-21 12:13 kernel test robot
2023-12-28 14:30 kernel test robot
2023-12-04 8:56 kernel test robot
2023-11-16 6:03 kernel test robot
2023-11-05 5:02 kernel test robot
2023-11-05 20:08 ` Chris Packham
2023-11-06 18:07 ` Andy Shevchenko
[not found] ` <CAHp75VfmUXgx3nkFR=dZqffOu-LSnU_9u9GRYy0bTPLcdYhHbg@mail.gmail.com>
[not found] ` <ZUdFtJeXBtx/httL@rli9-mobl>
[not found] ` <abdb00c4-c2f1-96e6-9731-5a1773099336@axentia.se>
2023-11-07 19:59 ` Andy Shevchenko
2023-11-07 21:39 ` Peter Rosin
2023-11-09 13:59 ` Andy Shevchenko
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=ZZlr48NanPRkmkgl@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.