From: David Miller <davem@davemloft.net>
To: brakmo@fb.com
Cc: netdev@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH net-next] bpf: Rename tcp_bbf.readme to tcp_bpf.readme
Date: Wed, 08 Nov 2017 12:15:55 +0900 (KST) [thread overview]
Message-ID: <20171108.121555.1629362209372788450.davem@davemloft.net> (raw)
In-Reply-To: <20171106024410.2172338-1-brakmo@fb.com>
From: Lawrence Brakmo <brakmo@fb.com>
Date: Sun, 5 Nov 2017 18:44:10 -0800
> The original patch had the wrong filename.
>
> Fixes: bfdf75693875 ("bpf: create samples/bpf/tcp_bpf.readme")
> Signed-off-by: Lawrence Brakmo <brakmo@fb.com>
Applied, thank you.
prev parent reply other threads:[~2017-11-08 3:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 2:44 [PATCH net-next] bpf: Rename tcp_bbf.readme to tcp_bpf.readme Lawrence Brakmo
2017-11-06 5:22 ` Alexei Starovoitov
2017-11-06 5:29 ` Daniel Borkmann
2017-11-08 3:15 ` David Miller [this message]
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=20171108.121555.1629362209372788450.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=brakmo@fb.com \
--cc=kernel-team@fb.com \
--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).