From: Stefano Brivio <sbrivio@redhat.com>
To: Andrea Claudi <aclaudi@redhat.com>
Cc: netdev@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net
Subject: Re: [PATCH bpf-next] bpf: remove useless variable
Date: Fri, 14 Dec 2018 12:24:59 +0100 [thread overview]
Message-ID: <20181214122459.2938ce9f@redhat.com> (raw)
In-Reply-To: <f045945073f2d9698939ca7a0ec4bab3af1cb6e8.1544724747.git.aclaudi@redhat.com>
On Thu, 13 Dec 2018 22:44:57 +0100
Andrea Claudi <aclaudi@redhat.com> wrote:
> bytes is initialized to end - start at the beginning of this function,
> and is never changed. Remove it making the code a bit more readable.
>
> Suggested-by: Stefano Brivio <sbrivio@redhat.com>
> Signed-off-by: Andrea Claudi <aclaudi@redhat.com>
Reviewed-by: Stefano Brivio <sbrivio@redhat.com>
--
Stefano
next prev parent reply other threads:[~2018-12-14 11:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 21:44 [PATCH bpf-next] bpf: remove useless variable Andrea Claudi
2018-12-14 11:24 ` Stefano Brivio [this message]
2018-12-14 17:03 ` Martin Lau
2018-12-14 17:14 ` Stefano Brivio
2018-12-15 1:13 ` 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=20181214122459.2938ce9f@redhat.com \
--to=sbrivio@redhat.com \
--cc=aclaudi@redhat.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.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).