mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yang Jihong <yangjihong1@huawei.com>
To: Paolo Abeni <pabeni@redhat.com>, <davem@davemloft.net>,
	<edumazet@google.com>, <kuba@kernel.org>, <keescook@chromium.org>,
	<gustavoars@kernel.org>, <netdev@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <bpf@vger.kernel.org>,
	<acme@kernel.org>
Subject: Re: [PATCH] uapi: Add missing linux/stddef.h header file to in.h
Date: Thu, 3 Nov 2022 16:59:02 +0800	[thread overview]
Message-ID: <300b547d-8ea5-d7d1-f39e-d55df73847cd@huawei.com> (raw)
In-Reply-To: <477a37b80b01d5eaa895effa20df29bcf02f65b6.camel@redhat.com>

Hello Paolo,

On 2022/11/3 16:25, Paolo Abeni wrote:
> On Mon, 2022-10-31 at 17:55 +0800, Yang Jihong wrote:
>> commit 5854a09b4957 ("net/ipv4: Use __DECLARE_FLEX_ARRAY() helper") does not
>> include "linux/stddef.h" header file, and tools headers update linux/in.h copy,
>> BPF prog fails to be compiled:
>>
>>      CLNG-BPF [test_maps] bpf_flow.bpf.o
>>      CLNG-BPF [test_maps] cgroup_skb_sk_lookup_kern.bpf.o
>>    In file included from progs/cgroup_skb_sk_lookup_kern.c:9:
>>    /root/linux/tools/include/uapi/linux/in.h:199:3: error: type name requires a specifier or qualifier
>>                    __DECLARE_FLEX_ARRAY(__be32, imsf_slist_flex);
>>                    ^
>>    /root/linux/tools/include/uapi/linux/in.h:199:32: error: type specifier missing, defaults to 'int' [-Werror,-Wimplicit-int]
>>                    __DECLARE_FLEX_ARRAY(__be32, imsf_slist_flex);
>>                                                 ^
>>    2 errors generated.
>>
>> To maintain consistency, add missing header file to kernel.
>> Fixes: 5854a09b4957 ("net/ipv4: Use __DECLARE_FLEX_ARRAY() helper")
>>
>> Signed-off-by: Yang Jihong <yangjihong1@huawei.com>
> 
> The 'Fixes' tag must be separated by the commit message by a blank
> line, and you need to remove the empty line between 'Fixes' and SoB.
> 
> Additionally, on repost, please specify the target tree in the patch
> subj, and wrap the commit message text to 75 chars per line (that does
> not apply to the build output).
> 
OK, will fix these issues in the next version, thanks for your advice.


Thanks,
Yang
> Thanks,
> 
> Paolo
> 
> 
> .
> 

      reply	other threads:[~2022-11-03  8:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31  9:55 Yang Jihong
2022-11-03  8:25 ` Paolo Abeni
2022-11-03  8:59   ` Yang Jihong [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=300b547d-8ea5-d7d1-f39e-d55df73847cd@huawei.com \
    --to=yangjihong1@huawei.com \
    --cc=acme@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gustavoars@kernel.org \
    --cc=keescook@chromium.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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®