From: Al Viro <viro@zeniv.linux.org.uk>
To: kernel test robot <lkp@intel.com>
Cc: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>,
Evgeniy Dushistov <dushistov@mail.ru>,
Ira Weiny <ira.weiny@intel.com>,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
linux-fsdevel@vger.kernel.org, llvm@lists.linux.dev,
oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH 3/3] fs/ufs: Replace kmap() with kmap_local_page()
Date: Mon, 12 Dec 2022 01:07:31 +0000 [thread overview]
Message-ID: <Y5Z+05hRftbI0mxk@ZenIV> (raw)
In-Reply-To: <202212120803.iPhHqCqR-lkp@intel.com>
On Mon, Dec 12, 2022 at 08:52:47AM +0800, kernel test robot wrote:
> >> fs/ufs/dir.c:210:22: warning: variable 'kaddr' is uninitialized when used here [-Wuninitialized]
> ufs_put_page(*page, kaddr);
> ^~~~~
> fs/ufs/dir.c:196:13: note: initialize the variable 'kaddr' to silence this warning
> char *kaddr;
> ^
> = NULL
> 1 warning generated.
Warning is right, suggestion - worse than useless...
next prev parent reply other threads:[~2022-12-12 1:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-11 21:31 [PATCH 0/3] fs/ufs: replace kmap() with kmap_local_page() Fabio M. De Francesco
2022-12-11 21:31 ` [PATCH 1/3] fs/ufs: Use the offset_in_page() helper Fabio M. De Francesco
2022-12-11 21:31 ` [PATCH 2/3] fs/ufs: Change the signature of ufs_get_page() Fabio M. De Francesco
2022-12-11 22:29 ` Al Viro
2022-12-11 23:56 ` Fabio M. De Francesco
2022-12-11 22:42 ` Al Viro
2022-12-12 20:08 ` Fabio M. De Francesco
2022-12-11 21:31 ` [PATCH 3/3] fs/ufs: Replace kmap() with kmap_local_page() Fabio M. De Francesco
2022-12-11 22:39 ` Al Viro
2022-12-12 0:14 ` Fabio M. De Francesco
2022-12-12 0:52 ` kernel test robot
2022-12-12 1:07 ` Al Viro [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-12 14:00 kernel test robot
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=Y5Z+05hRftbI0mxk@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=bpf@vger.kernel.org \
--cc=dushistov@mail.ru \
--cc=fmdefrancesco@gmail.com \
--cc=ira.weiny@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--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.