From: Daniel Borkmann <daniel@iogearbox.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Alexei Starovoitov <ast@kernel.org>,
Networking <netdev@vger.kernel.org>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the bpf-next tree
Date: Sat, 1 Sep 2018 02:06:00 +0200 [thread overview]
Message-ID: <5bfa0d9e-bbe3-5a63-0857-8129a9053628@iogearbox.net> (raw)
In-Reply-To: <20180901050751.3714fc63@canb.auug.org.au>
On 08/31/2018 09:07 PM, Stephen Rothwell wrote:
> Hi all,
>
> Commits
>
> 0f93c3995c93 ("bpf: add TCP_SAVE_SYN/TCP_SAVED_SYN sample program")
> 9452048c7940 ("bpf: add TCP_SAVE_SYN/TCP_SAVED_SYN options for bpf_(set|get)sockopt")
> 175eba5962b4 ("xdp: remove redundant variable 'headroom'")
>
> are missing a Signed-off-by from their committers.
Fixed up, thanks!
next prev parent reply other threads:[~2018-09-01 0:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-31 19:07 linux-next: Signed-off-by missing for commit in the bpf-next tree Stephen Rothwell
2018-09-01 0:06 ` Daniel Borkmann [this message]
2022-11-22 21:24 Stephen Rothwell
2022-11-22 21:35 ` Alexei Starovoitov
2023-12-07 21:47 Stephen Rothwell
2023-12-07 21:57 ` Andrii Nakryiko
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=5bfa0d9e-bbe3-5a63-0857-8129a9053628@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).