All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Arnd Bergmann <arnd@kernel.org>
Cc: l.stelmach@samsung.com, davem@davemloft.net, kuba@kernel.org,
	jgg@ziepe.ca, arnd@arndb.de, nathan@kernel.org, alobakin@pm.me,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] ax88796c: fix ioctl callback
Date: Fri, 05 Nov 2021 14:30:07 +0000	[thread overview]
Message-ID: <163612260776.32748.4456572271474269770.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211105092954.1771974-1-arnd@kernel.org>

Hello:

This series was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:

On Fri,  5 Nov 2021 10:29:39 +0100 you wrote:
> From: Arnd Bergmann <arnd@arndb.de>
> 
> The timestamp ioctls are now handled by the ndo_eth_ioctl() callback,
> not the old ndo_do_ioctl(), but oax88796 introduced the
> function for the old way.
> 
> Move it over to ndo_eth_ioctl() to actually allow calling it from
> user space.
> 
> [...]

Here is the summary with links:
  - [1/2] ax88796c: fix ioctl callback
    https://git.kernel.org/netdev/net/c/9dcc00715a7c
  - [2/2] octeontx2-nicvf: fix ioctl callback
    https://git.kernel.org/netdev/net/c/a6785bd7d83c

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



      parent reply	other threads:[~2021-11-05 14:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20211105131932eucas1p284bdb650732ceff3c8326ed578f22b1a@eucas1p2.samsung.com>
2021-11-05  9:29 ` [PATCH 1/2] ax88796c: fix ioctl callback Arnd Bergmann
2021-11-05  9:29   ` [PATCH 2/2] octeontx2-nicvf: " Arnd Bergmann
2021-11-05 13:19   ` [PATCH 1/2] ax88796c: " Lukasz Stelmach
2021-11-05 14: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=163612260776.32748.4456572271474269770.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alobakin@pm.me \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=davem@davemloft.net \
    --cc=jgg@ziepe.ca \
    --cc=kuba@kernel.org \
    --cc=l.stelmach@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathan@kernel.org \
    --cc=netdev@vger.kernel.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 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.