All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: Song Liu <liu.song.a23@gmail.com>, lizhijian@cn.fujitsu.com
Cc: shuah@kernel.org, Networking <netdev@vger.kernel.org>,
	linux-kselftest@vger.kernel.org,
	open list <linux-kernel@vger.kernel.org>,
	Alexei Starovoitov <ast@kernel.org>
Subject: Re: [PATCH v2] kselftests/bpf: use ping6 as the default ipv6 ping binary if it exists
Date: Wed, 31 Oct 2018 23:11:23 +0100	[thread overview]
Message-ID: <9244917c-05d7-113d-fef8-ff5251c8e0fe@iogearbox.net> (raw)
In-Reply-To: <CAPhsuW4Bm2H7sV8xgzcD9s=9d_z1bpeEYbo2OMTTh9mcgmrC0w@mail.gmail.com>

On 10/30/2018 07:35 PM, Song Liu wrote:
> On Mon, Oct 29, 2018 at 7:35 PM Li Zhijian <lizhijian@cn.fujitsu.com> wrote:
>>
>> ping binary on some distros doesn't support "ping -6" anymore.
>>
>> Signed-off-by: Li Zhijian <lizhijian@cn.fujitsu.com>
> 
> I think this should go bpf-next. Please resubmit when the bpf-next tree is open
> (after the merge window). Other than this:
> 
> Acked-by: Song Liu <songliubraving@fb.com>

Ok, applied to bpf tree, thanks. Given the fix, though not too urgent perhaps,
is small and isolated enough, I've applied it there.

WARNING: multiple messages have this Message-ID (diff)
From: daniel at iogearbox.net (Daniel Borkmann)
Subject: [PATCH v2] kselftests/bpf: use ping6 as the default ipv6 ping binary if it exists
Date: Wed, 31 Oct 2018 23:11:23 +0100	[thread overview]
Message-ID: <9244917c-05d7-113d-fef8-ff5251c8e0fe@iogearbox.net> (raw)
In-Reply-To: <CAPhsuW4Bm2H7sV8xgzcD9s=9d_z1bpeEYbo2OMTTh9mcgmrC0w@mail.gmail.com>

On 10/30/2018 07:35 PM, Song Liu wrote:
> On Mon, Oct 29, 2018 at 7:35 PM Li Zhijian <lizhijian at cn.fujitsu.com> wrote:
>>
>> ping binary on some distros doesn't support "ping -6" anymore.
>>
>> Signed-off-by: Li Zhijian <lizhijian at cn.fujitsu.com>
> 
> I think this should go bpf-next. Please resubmit when the bpf-next tree is open
> (after the merge window). Other than this:
> 
> Acked-by: Song Liu <songliubraving at fb.com>

Ok, applied to bpf tree, thanks. Given the fix, though not too urgent perhaps,
is small and isolated enough, I've applied it there.

WARNING: multiple messages have this Message-ID (diff)
From: daniel@iogearbox.net (Daniel Borkmann)
Subject: [PATCH v2] kselftests/bpf: use ping6 as the default ipv6 ping binary if it exists
Date: Wed, 31 Oct 2018 23:11:23 +0100	[thread overview]
Message-ID: <9244917c-05d7-113d-fef8-ff5251c8e0fe@iogearbox.net> (raw)
Message-ID: <20181031221123.Ei7KaH2Kgw8ixYgr4hg2iW2NK9nic0X411M1LAopBO4@z> (raw)
In-Reply-To: <CAPhsuW4Bm2H7sV8xgzcD9s=9d_z1bpeEYbo2OMTTh9mcgmrC0w@mail.gmail.com>

On 10/30/2018 07:35 PM, Song Liu wrote:
> On Mon, Oct 29, 2018@7:35 PM Li Zhijian <lizhijian@cn.fujitsu.com> wrote:
>>
>> ping binary on some distros doesn't support "ping -6" anymore.
>>
>> Signed-off-by: Li Zhijian <lizhijian at cn.fujitsu.com>
> 
> I think this should go bpf-next. Please resubmit when the bpf-next tree is open
> (after the merge window). Other than this:
> 
> Acked-by: Song Liu <songliubraving at fb.com>

Ok, applied to bpf tree, thanks. Given the fix, though not too urgent perhaps,
is small and isolated enough, I've applied it there.

  reply	other threads:[~2018-10-31 22:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-30  3:15 [PATCH v2] kselftests/bpf: use ping6 as the default ipv6 ping binary if it exists Li Zhijian
2018-10-30  3:15 ` Li Zhijian
2018-10-30  3:15 ` lizhijian
2018-10-30 18:35 ` Song Liu
2018-10-30 18:35   ` Song Liu
2018-10-30 18:35   ` liu.song.a23
2018-10-31 22:11   ` Daniel Borkmann [this message]
2018-10-31 22:11     ` Daniel Borkmann
2018-10-31 22:11     ` daniel

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=9244917c-05d7-113d-fef8-ff5251c8e0fe@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=ast@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=liu.song.a23@gmail.com \
    --cc=lizhijian@cn.fujitsu.com \
    --cc=netdev@vger.kernel.org \
    --cc=shuah@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.