From: Jan Kara <jack@suse.cz>
To: kernel test robot <lkp@intel.com>
Cc: Jan Kara <jack@suse.cz>, oe-kbuild-all@lists.linux.dev
Subject: Re: fs/quota/quota_tree.c:674:8: warning: variable 'blk' is uninitialized when used here
Date: Mon, 12 Feb 2024 14:16:15 +0100 [thread overview]
Message-ID: <20240212131615.6jvnwweivkydv3j7@quack3> (raw)
In-Reply-To: <202402101306.SBcbZx79-lkp@intel.com>
On Sat 10-02-24 14:01:32, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git for_next
> head: 71b12545f603de39a967b52287c29ede3f85ff2f
> commit: 223bfb57631b10036e55579ecb5718123fa41c8c quota: Detect loops in quota tree
> date: 19 hours ago
> config: i386-randconfig-141-20240210 (https://download.01.org/0day-ci/archive/20240210/202402101306.SBcbZx79-lkp@intel.com/config)
> compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240210/202402101306.SBcbZx79-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/202402101306.SBcbZx79-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> >> fs/quota/quota_tree.c:674:8: warning: variable 'blk' is uninitialized when used here [-Wuninitialized]
> 674 | blk);
> | ^~~
Thanks. Fixed up in my tree.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2024-02-12 13:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-10 6:01 fs/quota/quota_tree.c:674:8: warning: variable 'blk' is uninitialized when used here kernel test robot
2024-02-12 13:16 ` Jan Kara [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=20240212131615.6jvnwweivkydv3j7@quack3 \
--to=jack@suse.cz \
--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.