netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Tobias Klauser <tklauser@distanz.ch>
Cc: davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
	David.Laight@ACULAB.COM, hmukos@yandex-team.ru,
	netdev@vger.kernel.org
Subject: Re: [PATCH v3] socket: Don't use u8 type in uapi socket.h
Date: Thu, 02 Jun 2022 00:40:12 +0000	[thread overview]
Message-ID: <165413041219.18481.5655890932630615236.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220531094345.13801-1-tklauser@distanz.ch>

Hello:

This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Tue, 31 May 2022 11:43:45 +0200 you wrote:
> Use plain 255 instead, which also avoid introducing an additional header
> dependency on <linux/types.h>
> 
> Fixes: 26859240e4ee ("txhash: Add socket option to control TX hash rethink behavior")
> Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
> ---
> v3: changed to plain 255 as suggested by David Laight and Paolo Abeni
> 
> [...]

Here is the summary with links:
  - [v3] socket: Don't use u8 type in uapi socket.h
    https://git.kernel.org/netdev/net/c/8d3398ba2a0d

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



      reply	other threads:[~2022-06-02  0:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-25  8:51 [PATCH] socket: Use __u8 instead of u8 in uapi socket.h Tobias Klauser
2022-05-25 13:21 ` kernel test robot
2022-05-30  8:14 ` [PATCH v2] " Tobias Klauser
2022-05-30  8:20   ` David Laight
2022-05-31  9:24     ` Paolo Abeni
2022-05-31  9:44       ` Tobias Klauser
2022-05-31  9:43 ` [PATCH v3] socket: Don't use u8 type " Tobias Klauser
2022-06-02  0:40   ` 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=165413041219.18481.5655890932630615236.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=David.Laight@ACULAB.COM \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hmukos@yandex-team.ru \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=tklauser@distanz.ch \
    /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).