mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Arushi Singhal <arushisinghal19971997@gmail.com>
Cc: kbuild-all@01.org, w.d.hubbs@gmail.com,
	devel@driverdev.osuosl.org, Kirk Reiser <kirk@reisers.ca>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	speakup@linux-speakup.org, linux-kernel@vger.kernel.org,
	outreachy-kernel@googlegroups.com,
	Samuel Thibault <samuel.thibault@ens-lyon.org>,
	Chris Brannon <chris@the-brannons.com>
Subject: Re: [PATCH] staging: speakup: else is not generally useful after a break or return
Date: Mon, 6 Mar 2017 20:59:13 +0800	[thread overview]
Message-ID: <201703062042.2wJkZ1BS%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170303155557.GA23744@arushi-HP-Pavilion-Notebook>

[-- Attachment #1: Type: text/plain, Size: 2341 bytes --]

Hi Arushi,

[auto build test WARNING on staging/staging-testing]
[cannot apply to v4.11-rc1 next-20170306]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Arushi-Singhal/staging-speakup-else-is-not-generally-useful-after-a-break-or-return/20170306-072009
config: openrisc-allmodconfig (attached as .config)
compiler: or32-linux-gcc (GCC) 4.5.1-or32-1.0rc1
reproduce:
        wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        make.cross ARCH=openrisc 

All warnings (new ones prefixed by >>):

   drivers/staging/speakup/keyhelp.c: In function 'spk_handle_help':
>> drivers/staging/speakup/keyhelp.c:146:19: warning: unused variable 'val'
>> drivers/staging/speakup/keyhelp.c:146:11: warning: unused variable 'p_keys'
>> drivers/staging/speakup/keyhelp.c:145:9: warning: unused variable 'func'
>> drivers/staging/speakup/keyhelp.c:143:9: warning: unused variable 'n'

vim +/val +146 drivers/staging/speakup/keyhelp.c

c6e3fd22c William Hubbs   2010-10-07  137  	}
c6e3fd22c William Hubbs   2010-10-07  138  	return 0;
c6e3fd22c William Hubbs   2010-10-07  139  }
c6e3fd22c William Hubbs   2010-10-07  140  
ca2beaf84 Samuel Thibault 2013-01-02  141  int spk_handle_help(struct vc_data *vc, u_char type, u_char ch, u_short key)
c6e3fd22c William Hubbs   2010-10-07  142  {
c6e3fd22c William Hubbs   2010-10-07 @143  	int i, n;
c6e3fd22c William Hubbs   2010-10-07  144  	char *name;
c6e3fd22c William Hubbs   2010-10-07 @145  	u_char func, *kp;
c6e3fd22c William Hubbs   2010-10-07 @146  	u_short *p_keys, val;
8e69a8110 Domagoj Trsan   2014-09-09  147  
c6e3fd22c William Hubbs   2010-10-07  148  	if (letter_offsets[0] == -1)
c6e3fd22c William Hubbs   2010-10-07  149  		help_init();

:::::: The code at line 146 was first introduced by commit
:::::: c6e3fd22cd538365bfeb82997d5b89562e077d42 Staging: add speakup to the staging directory

:::::: TO: William Hubbs <w.d.hubbs@gmail.com>
:::::: CC: Greg Kroah-Hartman <gregkh@suse.de>

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 40416 bytes --]

      parent reply	other threads:[~2017-03-06 13:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-03 15:55 Arushi Singhal
2017-03-03 16:03 ` [Outreachy kernel] " Julia Lawall
     [not found]   ` <cc06f004-d16e-4e67-86fb-5e1b099c811a@googlegroups.com>
2017-03-03 16:54     ` Julia Lawall
2017-03-03 17:48   ` Dan Carpenter
2017-03-06 12:59 ` kbuild 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=201703062042.2wJkZ1BS%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=arushisinghal19971997@gmail.com \
    --cc=chris@the-brannons.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kbuild-all@01.org \
    --cc=kirk@reisers.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=outreachy-kernel@googlegroups.com \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=speakup@linux-speakup.org \
    --cc=w.d.hubbs@gmail.com \
    /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®