From: patchwork-bot+netdevbpf@kernel.org
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: mkl@pengutronix.de, davem@davemloft.net, kuba@kernel.org,
socketcan@hartkopp.net, robin@protonic.nl,
syzbot+5138c4dd15a0401bec7b@syzkaller.appspotmail.com,
kernel@pengutronix.de, linux-can@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v4 1/1] net: introduce CAN specific pointer in the struct net_device
Date: Thu, 25 Feb 2021 00:10:11 +0000 [thread overview]
Message-ID: <161421181172.15909.1583905121942567968.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210223070127.4538-1-o.rempel@pengutronix.de>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Tue, 23 Feb 2021 08:01:26 +0100 you wrote:
> Since 20dd3850bcf8 ("can: Speed up CAN frame receiption by using
> ml_priv") the CAN framework uses per device specific data in the AF_CAN
> protocol. For this purpose the struct net_device->ml_priv is used. Later
> the ml_priv usage in CAN was extended for other users, one of them being
> CAN_J1939.
>
> Later in the kernel ml_priv was converted to an union, used by other
> drivers. E.g. the tun driver started storing it's stats pointer.
>
> [...]
Here is the summary with links:
- [net,v4,1/1] net: introduce CAN specific pointer in the struct net_device
https://git.kernel.org/netdev/net/c/4e096a18867a
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-02-25 0:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 7:01 [PATCH net v4 1/1] net: introduce CAN specific pointer in the struct net_device Oleksij Rempel
2021-02-25 0:10 ` 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=161421181172.15909.1583905121942567968.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=robin@protonic.nl \
--cc=socketcan@hartkopp.net \
--cc=syzbot+5138c4dd15a0401bec7b@syzkaller.appspotmail.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).