From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Greg KH <greg@kroah•com>, Julia Lawall <Julia.Lawall@lip6•fr>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: linux-next: build warnings after merge of the staging tree
Date: Wed, 6 May 2015 14:10:50 +1000 [thread overview]
Message-ID: <20150506141050.5689c298@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 807 bytes --]
Hi Greg,
After merging the staging tree, today's linux-next build (x86_64
allmodconfig) produced these warnings:
drivers/staging/lustre/lustre/llite/file.c: In function 'll_iocontrol_unregister':
drivers/staging/lustre/lustre/llite/file.c:3249:17: warning: unused variable 'size' [-Wunused-variable]
unsigned int size = tmp->iocd_size;
^
drivers/staging/lustre/lustre/llite/llite_lib.c: In function 'll_fill_super':
drivers/staging/lustre/lustre/llite/llite_lib.c:912:12: warning: unused variable 'instlen' [-Wunused-variable]
const int instlen = sizeof(cfg->cfg_instance) * 2 + 2;
^
Introduced by commit 97903a26fcfc ("staging: lustre: llite: drop uses
of OBD free functions").
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2015-05-06 4:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 4:10 Stephen Rothwell [this message]
2015-05-06 6:56 ` linux-next: build warnings after merge of the staging tree Julia Lawall
-- strict thread matches above, loose matches on Subject: below --
2019-02-05 3:22 Stephen Rothwell
2019-02-05 10:24 ` Jonathan Cameron
2018-05-14 4:34 Stephen Rothwell
2018-05-14 9:26 ` Greg KH
2017-11-02 4:38 Stephen Rothwell
2017-07-31 5:02 Stephen Rothwell
2017-08-09 1:25 ` Stephen Rothwell
2017-08-22 1:49 ` Stephen Rothwell
2017-08-17 17:57 ` Greg KH
2017-08-18 12:02 ` JB Van Puyvelde
2015-05-29 10:40 Stephen Rothwell
2015-06-01 8:50 ` Stephen Rothwell
2015-06-20 10:48 ` Stephen Rothwell
2015-06-20 14:50 ` Greg KH
2012-01-31 3:25 Stephen Rothwell
2012-01-31 5:14 ` Greg KH
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=20150506141050.5689c298@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=Julia.Lawall@lip6$(echo .)fr \
--cc=greg@kroah$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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