From: Joe Perches <joe@perches.com>
To: Ozgur Karatas <okaratas@member.fsf.org>,
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 10:35:21 -0800 [thread overview]
Message-ID: <1481913321.29291.89.camel@perches.com> (raw)
In-Reply-To: <5194151481912505@web1g.yandex.ru>
On Fri, 2016-12-16 at 20:21 +0200, Ozgur Karatas wrote:
> This patch fixed to keyboard typo, brackets not closed.
> I think, it should be close to parenthes.
No.
Please compile and test your patches on your own system
before you send them.
next prev parent reply other threads:[~2016-12-16 18:35 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 [this message]
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
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=1481913321.29291.89.camel@perches.com \
--to=joe@perches.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=okaratas@member.fsf.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