[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <88682469-61e8-bb26-9f93-8a939c250f0e@netronome.com>
Date: Mon, 30 Apr 2018 16:16:34 +0100
From: Quentin Monnet <quentin.monnet@...ronome.com>
To: David Ahern <dsahern@...il.com>,
Alexei Starovoitov <alexei.starovoitov@...il.com>
Cc: daniel@...earbox.net, ast@...nel.org, netdev@...r.kernel.org,
oss-drivers@...ronome.com, Yonghong Song <yhs@...com>
Subject: Re: [PATCH bpf-next 2/3] bpf: fix formatting for bpf_get_stack()
helper doc
2018-04-30 09:12 UTC-0600 ~ David Ahern <dsahern@...il.com>
> On 4/30/18 9:08 AM, Alexei Starovoitov wrote:
>>> diff --git a/include/uapi/linux/bpf.h b/include/uapi/linux/bpf.h
>>> index 530ff6588d8f..8daef7326bb7 100644
>>> --- a/include/uapi/linux/bpf.h
>>> +++ b/include/uapi/linux/bpf.h
>>> @@ -1770,33 +1770,33 @@ union bpf_attr {
>>> *
>>> * int bpf_get_stack(struct pt_regs *regs, void *buf, u32 size, u64 flags)
>>> * Description
>>> - * Return a user or a kernel stack in bpf program provided buffer.
>>> - * To achieve this, the helper needs *ctx*, which is a pointer
>>> + * Return a user or a kernel stack in bpf program provided buffer.
>>> + * To achieve this, the helper needs *ctx*, which is a pointer
>> I still don't quite get the difference.
>> It's replacing 2 tabs in above with 1 space + 2 tabs ?
Yes, exactly (Plus in this case, the "::" a few line below has a missing
tab).
>> Can you please teach the python script to accept both?
>> I bet that will be recurring mistake and it's impossible to spot in code review.
> And checkpatch throws an error on the 1 space + 2 tabs so it gets
> confusing on which format should be used.
Sorry about that :/. I will send a patch to make the script more flexible.
Quentin
Powered by blists - more mailing lists