From: patchwork-bot+netdevbpf@kernel.org
To: Arnd Bergmann <arnd@kernel.org>
Cc: netdev@vger.kernel.org, arnd@arndb.de, viro@zeniv.linux.org.uk,
andrew@lunn.ch, hch@lst.de, dsahern@kernel.org,
davem@davemloft.net, edumazet@google.com,
yoshfuji@linux-ipv6.org, kuba@kernel.org, keescook@chromium.org,
elver@google.com, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org
Subject: Re: [PATCH net-next v6 0/6] remove compat_alloc_user_space()
Date: Fri, 23 Jul 2021 14:40:05 +0000 [thread overview]
Message-ID: <162705120552.20178.10414947858942867479.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210722142903.213084-1-arnd@kernel.org>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Thu, 22 Jul 2021 16:28:57 +0200 you wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> This is the fifth version of my series, now spanning four patches
> instead of two, with a new approach for handling struct ifreq
> compatibility after I realized that my earlier approach introduces
> additional problems.
>
> [...]
Here is the summary with links:
- [net-next,v6,1/6] compat: make linux/compat.h available everywhere
https://git.kernel.org/netdev/net-next/c/1a33b18b3bd9
- [net-next,v6,2/6] ethtool: improve compat ioctl handling
https://git.kernel.org/netdev/net-next/c/dd98d2895de6
- [net-next,v6,3/6] net: socket: rework SIOC?IFMAP ioctls
https://git.kernel.org/netdev/net-next/c/709566d79209
- [net-next,v6,4/6] net: socket: remove register_gifconf
https://git.kernel.org/netdev/net-next/c/b0e99d03778b
- [net-next,v6,5/6] net: socket: simplify dev_ifconf handling
https://git.kernel.org/netdev/net-next/c/876f0bf9d0d5
- [net-next,v6,6/6] net: socket: rework compat_ifreq_ioctl()
https://git.kernel.org/netdev/net-next/c/29c4964822aa
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-07-23 14:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 14:28 [PATCH net-next v6 0/6] remove compat_alloc_user_space() Arnd Bergmann
2021-07-22 14:28 ` [PATCH net-next v6 1/6] compat: make linux/compat.h available everywhere Arnd Bergmann
2021-07-22 16:22 ` Christoph Hellwig
2021-07-22 14:28 ` [PATCH net-next v6 2/6] ethtool: improve compat ioctl handling Arnd Bergmann
2021-07-23 23:50 ` Shannon Nelson
2021-07-22 14:29 ` [PATCH net-next v6 3/6] net: socket: rework SIOC?IFMAP ioctls Arnd Bergmann
2021-07-22 14:29 ` [PATCH net-next v6 4/6] net: socket: remove register_gifconf Arnd Bergmann
2021-07-22 16:24 ` Christoph Hellwig
2021-07-22 14:29 ` [PATCH net-next v6 5/6] net: socket: simplify dev_ifconf handling Arnd Bergmann
2021-07-22 16:26 ` Christoph Hellwig
2021-07-22 14:29 ` [PATCH net-next v6 6/6] net: socket: rework compat_ifreq_ioctl() Arnd Bergmann
2021-07-22 16:26 ` Christoph Hellwig
2021-07-23 14: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=162705120552.20178.10414947858942867479.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=elver@google.com \
--cc=hch@lst.de \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=yoshfuji@linux-ipv6.org \
/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).