From: Alexei Starovoitov <ast@plumgrid.com>
To: Daniel Borkmann <daniel@iogearbox.net>, davem@davemloft.net
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net: sched: don't break line in tc_classify loop notification
Date: Fri, 28 Aug 2015 10:00:35 -0700 [thread overview]
Message-ID: <55E093B3.2030308@plumgrid.com> (raw)
In-Reply-To: <4b24d2566b1877613540f277e60673c817b71842.1440780286.git.daniel@iogearbox.net>
On 8/28/15 9:46 AM, Daniel Borkmann wrote:
> Just some minor noise follow-up to address some stylistic issues of
> commit 3b3ae880266d ("net: sched: consolidate tc_classify{,_compat}").
> Accidentally v1 instead of v2 of that commit got applied, so this
> patch adds the relative diff.
>
> Suggested-by: Alexei Starovoitov<ast@plumgrid.com>
> Signed-off-by: Daniel Borkmann<daniel@iogearbox.net>
Acked-by: Alexei Starovoitov <ast@plumgrid.com>
next prev parent reply other threads:[~2015-08-28 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 16:46 [PATCH net-next] net: sched: don't break line in tc_classify loop notification Daniel Borkmann
2015-08-28 17:00 ` Alexei Starovoitov [this message]
2015-08-28 21:01 ` David Miller
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=55E093B3.2030308@plumgrid.com \
--to=ast@plumgrid.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.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).