netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Kuniyuki Iwashima <kuniyu@amazon.com>
Cc: <mhal@rbox.co>, <bpf@vger.kernel.org>, <davem@davemloft.net>,
	<edumazet@google.com>, <jakub@cloudflare.com>,
	<john.fastabend@gmail.com>, <netdev@vger.kernel.org>,
	<pabeni@redhat.com>
Subject: Re: [PATCH net] af_unix: Disable MSG_OOB handling for sockets in sockmap/sockhash
Date: Fri, 21 Jun 2024 17:02:32 -0700	[thread overview]
Message-ID: <20240621170232.74ce4a27@kernel.org> (raw)
In-Reply-To: <20240620221223.66096-1-kuniyu@amazon.com>

On Thu, 20 Jun 2024 15:12:23 -0700 Kuniyuki Iwashima wrote:
> Sorry for not mentioning this before, but could you replace "net" with
> "bpf" in Subject and rebase the patch on bpf.git so that we can trigger
> the patchwork's CI ?
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git

netdev runs the BPF CI, too, FWIW.

Open the patch in patchwork:
https://patchwork.kernel.org/project/netdevbpf/patch/20240620203009.2610301-1-mhal@rbox.co/
Click on contest in "checks".
Select Executor = "gh-bpf-ci".
Click on "outputs", you should get to:
https://github.com/kernel-patches/bpf/actions/runs/9607623089
If you click in context on the branch name it will take you to
the tested branch:
https://github.com/linux-netdev/testing/commits/net-next-2024-06-21--03-00
which had:
  af_unix: Disable MSG_OOB handling for sockets in sockmap/sockhash
applied, 5th from the top.

  reply	other threads:[~2024-06-22  0:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-20 20:20 [PATCH net] af_unix: Disable MSG_OOB handling for sockets in sockmap/sockhash Michal Luczaj
2024-06-20 22:12 ` Kuniyuki Iwashima
2024-06-22  0:02   ` Jakub Kicinski [this message]
2024-06-22 22:38   ` Michal Luczaj

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=20240621170232.74ce4a27@kernel.org \
    --to=kuba@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jakub@cloudflare.com \
    --cc=john.fastabend@gmail.com \
    --cc=kuniyu@amazon.com \
    --cc=mhal@rbox.co \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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 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).