linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: johannes@gnu-linux.rocks, jikos@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, benjamin.tissoires@redhat.com,
	linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
	andi.shyti@kernel.org, christophe.jaillet@wanadoo.fr,
	ak@it-klinger.de, Johannes Roith <johannes@gnu-linux.rocks>
Subject: Re: [PATCH v4] hid-mcp2200: added driver for GPIOs of MCP2200
Date: Fri, 18 Aug 2023 01:11:32 +0800	[thread overview]
Message-ID: <202308180056.nB1KSUap-lkp@intel.com> (raw)
In-Reply-To: <20230817091505.213318-1-johannes@gnu-linux.rocks>

Hi,

kernel test robot noticed the following build warnings:

[auto build test WARNING on hid/for-next]
[also build test WARNING on linus/master v6.5-rc6 next-20230817]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/johannes-gnu-linux-rocks/hid-mcp2200-added-driver-for-GPIOs-of-MCP2200/20230817-172246
base:   https://git.kernel.org/pub/scm/linux/kernel/git/hid/hid.git for-next
patch link:    https://lore.kernel.org/r/20230817091505.213318-1-johannes%40gnu-linux.rocks
patch subject: [PATCH v4] hid-mcp2200: added driver for GPIOs of MCP2200
config: sparc-allyesconfig (https://download.01.org/0day-ci/archive/20230818/202308180056.nB1KSUap-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230818/202308180056.nB1KSUap-lkp@intel.com/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/202308180056.nB1KSUap-lkp@intel.com/

All warnings (new ones prefixed by >>):

   drivers/hid/hid-mcp2200.c: In function 'mcp2200_remove':
>> drivers/hid/hid-mcp2200.c:395:25: warning: variable 'mcp' set but not used [-Wunused-but-set-variable]
     395 |         struct mcp2200 *mcp;
         |                         ^~~


vim +/mcp +395 drivers/hid/hid-mcp2200.c

   392	
   393	static void mcp2200_remove(struct hid_device *hdev)
   394	{
 > 395		struct mcp2200 *mcp;
   396	
   397		mcp = hid_get_drvdata(hdev);
   398	}
   399	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

      parent reply	other threads:[~2023-08-17 17:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-17  9:15 [PATCH v4] hid-mcp2200: added driver for GPIOs of MCP2200 johannes
2023-08-17 14:42 ` Randy Dunlap
2023-08-17 17:11 ` kernel test robot [this message]

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=202308180056.nB1KSUap-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=ak@it-klinger.de \
    --cc=andi.shyti@kernel.org \
    --cc=benjamin.tissoires@redhat.com \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=jikos@kernel.org \
    --cc=johannes@gnu-linux.rocks \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 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).