From: Ozgur Karatas <okaratas@member.fsf.org>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
David Miller <davem@davemloft.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH 1/1] tools: net: bpf_dbg.c fixed keyboard typo
Date: Fri, 16 Dec 2016 21:13:06 +0200 [thread overview]
Message-ID: <142441481915586@web39j.yandex.ru> (raw)
In-Reply-To: <96578fd4-dd02-f39a-a252-c37aa714d3d0@cogentembedded.com>
16.12.2016, 21:08, "Sergei Shtylyov" <sergei.shtylyov@cogentembedded.com>:
> Hello.
Hi
> On 12/16/2016 09:21 PM, Ozgur Karatas wrote:
>
>> This patch fixed to keyboard typo, brackets not closed.
>> I think, it should be close to parenthes.
>>
>> Signed-off-by: Ozgur Karatas <okaratas@member.fsf.org>
>> ---
>> tools/net/bpf_dbg.c | 2 +-
>> 1 files changed, 1 insertion(+), 1 deletions(-)
>>
>> diff --git a/tools/net/bpf_dbg.c b/tools/net/bpf_dbg.c
>> index 4f254bc..f715f46 100644
>> --- a/tools/net/bpf_dbg.c
>> +++ b/tools/net/bpf_dbg.c
>> @@ -1213,7 +1213,7 @@ static int cmd_disassemble(char *line_string)
>>
>> if (!bpf_prog_loaded())
>> return CMD_ERR;
>> - if (strlen(line_string) > 0 &&
>> + if (strlen(line_string) > 0 &&)
>
> Have tried to you compile that? :-/
Yes, i compiled but I apologize if there was NAK.
Also, checkpatch give a error.
I could be wrong, will review again.
Best Regards!
>> (line = strtoul(line_string, NULL, 10)) < bpf_prog_len)
>
> I think the code was correct before your patch...
>
>> single_line = true;
>> if (single_line)
>
> MBR, Sergei
~Ozgur
next prev parent reply other threads:[~2016-12-16 19:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-16 18:21 [PATCH 1/1] tools: net: bpf_dbg.c fixed keyboard typo Ozgur Karatas
2016-12-16 18:35 ` Joe Perches
2016-12-16 18:53 ` Ozgur Karatas
2016-12-16 18:58 ` Ozgur Karatas
2016-12-16 19:08 ` Sergei Shtylyov
2016-12-16 19:13 ` Ozgur Karatas [this message]
2016-12-16 19:31 ` Daniel Borkmann
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=142441481915586@web39j.yandex.ru \
--to=okaratas@member.fsf.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.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 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.