All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hangbin Liu <liuhangbin@gmail.com>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: netdev@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>,
	Yi-Hung Wei <yihung.wei@gmail.com>,
	David Miller <davem@davemloft.net>,
	bpf@vger.kernel.org, William Tu <u9012063@gmail.com>
Subject: Re: [PATCH net] selftests/bpf: set gopt opt_class to 0 if get tunnel opt failed
Date: Mon, 15 Mar 2021 14:57:34 +0800	[thread overview]
Message-ID: <20210315065734.GA2900@Leo-laptop-t470s> (raw)
In-Reply-To: <0b5c810b-5eec-c7b0-15fc-81c989494202@iogearbox.net>

On Fri, Mar 12, 2021 at 04:15:27PM +0100, Daniel Borkmann wrote:
> On 3/12/21 2:56 AM, Hangbin Liu wrote:
> > Hi David,
> > 
> > May I ask what's the status of this patch? From patchwork[1] the state is
> > accepted. But I can't find the fix on net or net-next.
> 
> I think there may have been two confusions, i) that $subject says that this goes
> via net tree instead of bpf tree, which might have caused auto-delegation to move
> this into 'netdev' patchwork reviewer bucket, and ii) the kernel patchwork bot then
> had a mismatch as you noticed when it checked net-next after tree merge and replied
> to the wrong patch of yours which then placed this one into 'accepted' state. I just
> delegated it to bpf and placed it back under review..
> 
> > [1] https://patchwork.kernel.org/project/netdevbpf/patch/20210309032214.2112438-1-liuhangbin@gmail.com/

Thanks Daniel, I thought the issue also exists on net tree and is a fixup. So
I set the target to 'net'.

Hangbin

  reply	other threads:[~2021-03-15  6:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-09  3:22 [PATCH net] selftests/bpf: set gopt opt_class to 0 if get tunnel opt failed Hangbin Liu
2021-03-09 18:53 ` William Tu
2021-03-10  1:37 ` patchwork-bot+netdevbpf
2021-03-10  7:09   ` Hangbin Liu
2021-03-12  1:56 ` Hangbin Liu
2021-03-12 15:15   ` Daniel Borkmann
2021-03-15  6:57     ` Hangbin Liu [this message]
2021-03-15 16:32       ` 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=20210315065734.GA2900@Leo-laptop-t470s \
    --to=liuhangbin@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=u9012063@gmail.com \
    --cc=yihung.wei@gmail.com \
    /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.