From: Pavel Machek <pavel@ucw.cz>
To: kernel test robot <lkp@intel.com>
Cc: "Marek Behún" <marek.behun@nic.cz>,
kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
linux-leds@vger.kernel.org
Subject: Re: [pavel-linux-leds:for-next 61/70] drivers/leds/leds-tca6507.c:750:34: warning: unused variable 'of_tca6507_leds_match'
Date: Fri, 25 Sep 2020 11:27:19 +0200 [thread overview]
Message-ID: <20200925092719.GA20659@amd> (raw)
In-Reply-To: <202009250524.By2seNuP%lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 336 bytes --]
Hi!
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
I patched it up and pushed the result.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
parent reply other threads:[~2020-09-25 9:27 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <202009250524.By2seNuP%lkp@intel.com>]
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=20200925092719.GA20659@amd \
--to=pavel@ucw.cz \
--cc=clang-built-linux@googlegroups.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-leds@vger.kernel.org \
--cc=lkp@intel.com \
--cc=marek.behun@nic.cz \
/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;
as well as URLs for NNTP newsgroup(s).