From: KP Singh <kpsingh@chromium.org>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, bpf <bpf@vger.kernel.org>,
LSM List <linux-security-module@vger.kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Martin KaFai Lau <kafai@fb.com>, Paul Turner <pjt@google.com>,
Jann Horn <jannh@google.com>,
Florent Revest <revest@chromium.org>
Subject: Re: [PATCH bpf-next v5 5/7] bpf: Implement bpf_local_storage for inodes
Date: Thu, 23 Jul 2020 13:52:02 +0200 [thread overview]
Message-ID: <6a907298-3355-d918-340c-10ef13d4d0d3@chromium.org> (raw)
In-Reply-To: <CAADnVQK=m18hgfuRZvykQiJPk_c+z=FR6Dpg0aRVvtJn6-Ckrw@mail.gmail.com>
On 23.07.20 07:18, Alexei Starovoitov wrote:
> On Wed, Jul 22, 2020 at 5:22 PM kernel test robot <lkp@intel.com> wrote:
>>
>
>> All warnings (new ones prefixed by >>):
>>
>> kernel/bpf/bpf_inode_storage.c: In function 'unlink_inode_storage':
>>>> kernel/bpf/bpf_inode_storage.c:34:32: warning: variable 'smap' set but not used [-Wunused-but-set-variable]
>
> KP,
>
> feel free to resubmit as soon as you fix the build.
> People typically ignore the patches when buildbot complains,
> since they know that maintainers are not going to apply a set with
> known build issue.
>
Got it. I need to get into the habit of building with W=1
(at least for the files I change).
Sent a v6 with the fix.
next prev parent reply other threads:[~2020-07-23 11:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 17:14 [PATCH bpf-next v5 0/7] Generalizing bpf_local_storage KP Singh
2020-07-22 17:14 ` [PATCH bpf-next v5 1/7] bpf: Renames to prepare for generalizing sk_storage KP Singh
2020-07-22 17:14 ` [PATCH bpf-next v5 2/7] bpf: Generalize caching for sk_storage KP Singh
2020-07-22 17:14 ` [PATCH bpf-next v5 3/7] bpf: Generalize bpf_sk_storage KP Singh
2020-07-22 17:14 ` [PATCH bpf-next v5 4/7] bpf: Split bpf_local_storage to bpf_sk_storage KP Singh
2020-07-22 17:14 ` [PATCH bpf-next v5 5/7] bpf: Implement bpf_local_storage for inodes KP Singh
2020-07-23 0:22 ` kernel test robot
2020-07-23 5:18 ` Alexei Starovoitov
2020-07-23 11:52 ` KP Singh [this message]
2020-07-22 17:14 ` [PATCH bpf-next v5 6/7] bpf: Allow local storage to be used from LSM programs KP Singh
2020-07-22 17:14 ` [PATCH bpf-next v5 7/7] bpf: Add selftests for local_storage KP Singh
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=6a907298-3355-d918-340c-10ef13d4d0d3@chromium.org \
--to=kpsingh@chromium.org \
--cc=alexei.starovoitov@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jannh@google.com \
--cc=kafai@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=pjt@google.com \
--cc=revest@chromium.org \
/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).