sparclinux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Anna Emese Nyiri <annaemesenyiri@gmail.com>
Cc: netdev@vger.kernel.org, fejes@inf.elte.hu, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, willemb@google.com,
	idosch@idosch.org, horms@kernel.org, dsahern@kernel.org,
	linux-can@vger.kernel.org, socketcan@hartkopp.net,
	mkl@pengutronix.de, linux-kselftest@vger.kernel.org,
	shuah@kernel.org, tsbogend@alpha.franken.de, kaiyuanz@google.com,
	James.Bottomley@HansenPartnership.com,
	richard.henderson@linaro.org, arnd@arndb.de,
	almasrymina@google.com, asml.silence@gmail.com,
	linux-mips@vger.kernel.org, andreas@gaisler.com,
	mattst88@gmail.com, kerneljasonxing@gmail.com,
	sparclinux@vger.kernel.org, linux-alpha@vger.kernel.org,
	linux-arch@vger.kernel.org, deller@gmx.de,
	vadim.fedorenko@linux.dev, linux-parisc@vger.kernel.org
Subject: Re: [PATCH net-next v7 0/4] Add support for SO_PRIORITY cmsg
Date: Tue, 17 Dec 2024 02:30:39 +0000	[thread overview]
Message-ID: <173440263998.420431.1463337451862804620.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241213084457.45120-1-annaemesenyiri@gmail.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Fri, 13 Dec 2024 09:44:53 +0100 you wrote:
> Introduce a new helper function, `sk_set_prio_allowed`,
> to centralize the logic for validating priority settings.
> Add support for the `SO_PRIORITY` control message,
> enabling user-space applications to set socket priority
> via control messages (cmsg).
> 
> Patch Overview:
> 
> [...]

Here is the summary with links:
  - [net-next,v7,1/4] sock: Introduce sk_set_prio_allowed helper function
    https://git.kernel.org/netdev/net-next/c/77ec16be758e
  - [net-next,v7,2/4] sock: support SO_PRIORITY cmsg
    https://git.kernel.org/netdev/net-next/c/a32f3e9d1ed1
  - [net-next,v7,3/4] selftests: net: test SO_PRIORITY ancillary data with cmsg_sender
    https://git.kernel.org/netdev/net-next/c/cda7d5abe089
  - [net-next,v7,4/4] sock: Introduce SO_RCVPRIORITY socket option
    (no matching commit)

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-12-17  2:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-13  8:44 [PATCH net-next v7 0/4] Add support for SO_PRIORITY cmsg Anna Emese Nyiri
2024-12-13  8:44 ` [PATCH net-next v7 1/4] sock: Introduce sk_set_prio_allowed helper function Anna Emese Nyiri
2024-12-13  8:44 ` [PATCH net-next v7 2/4] sock: support SO_PRIORITY cmsg Anna Emese Nyiri
2024-12-13  8:44 ` [PATCH net-next v7 3/4] selftests: net: test SO_PRIORITY ancillary data with cmsg_sender Anna Emese Nyiri
2024-12-13  8:44 ` [PATCH net-next v7 4/4] sock: Introduce SO_RCVPRIORITY socket option Anna Emese Nyiri
2024-12-17  2:20   ` Jakub Kicinski
2024-12-18 11:57     ` Anna Nyiri
2024-12-17  2:30 ` patchwork-bot+netdevbpf [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=173440263998.420431.1463337451862804620.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=almasrymina@google.com \
    --cc=andreas@gaisler.com \
    --cc=annaemesenyiri@gmail.com \
    --cc=arnd@arndb.de \
    --cc=asml.silence@gmail.com \
    --cc=deller@gmx.de \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=fejes@inf.elte.hu \
    --cc=horms@kernel.org \
    --cc=idosch@idosch.org \
    --cc=kaiyuanz@google.com \
    --cc=kerneljasonxing@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-alpha@vger.kernel.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=mattst88@gmail.com \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=richard.henderson@linaro.org \
    --cc=shuah@kernel.org \
    --cc=socketcan@hartkopp.net \
    --cc=sparclinux@vger.kernel.org \
    --cc=tsbogend@alpha.franken.de \
    --cc=vadim.fedorenko@linux.dev \
    --cc=willemb@google.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).