All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tobias Klauser <tklauser@distanz.ch>
To: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>,
	David Laight <David.Laight@ACULAB.COM>
Cc: Akhmat Karakotov <hmukos@yandex-team.ru>, netdev@vger.kernel.org
Subject: [PATCH v3] socket: Don't use u8 type in uapi socket.h
Date: Tue, 31 May 2022 11:43:45 +0200	[thread overview]
Message-ID: <20220531094345.13801-1-tklauser@distanz.ch> (raw)
In-Reply-To: <20220525085126.29977-1-tklauser@distanz.ch>

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

 include/uapi/linux/socket.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/uapi/linux/socket.h b/include/uapi/linux/socket.h
index 51d6bb2f6765..d3fcd3b5ec53 100644
--- a/include/uapi/linux/socket.h
+++ b/include/uapi/linux/socket.h
@@ -31,7 +31,7 @@ struct __kernel_sockaddr_storage {
 
 #define SOCK_BUF_LOCK_MASK (SOCK_SNDBUF_LOCK | SOCK_RCVBUF_LOCK)
 
-#define SOCK_TXREHASH_DEFAULT	((u8)-1)
+#define SOCK_TXREHASH_DEFAULT	255
 #define SOCK_TXREHASH_DISABLED	0
 #define SOCK_TXREHASH_ENABLED	1
 
-- 
2.36.1


  parent reply	other threads:[~2022-05-31  9:43 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 ` Tobias Klauser [this message]
2022-06-02  0:40   ` [PATCH v3] socket: Don't use u8 type " patchwork-bot+netdevbpf

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=20220531094345.13801-1-tklauser@distanz.ch \
    --to=tklauser@distanz.ch \
    --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 \
    /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.