From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: linux-can@vger.kernel.org,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: Re: [can-next v2] can: proc: remove pointers from CAN specific proc output
Date: Wed, 26 Aug 2026 13:28:51 +0200 [thread overview]
Message-ID: <20260826-soft-python-of-charisma-e981f4-mkl@pengutronix.de> (raw)
In-Reply-To: <20260815103400.117175-1-socketcan@hartkopp.net>
[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]
On 15.08.2026 12:34:00, Oliver Hartkopp wrote:
> - receive list 'rx_all':
> - (vcan3: no entry)
> - (vcan2: no entry)
> - (vcan1: no entry)
> - device can_id can_mask function userdata matches ident
> - vcan0 000 00000000 f88e6370 f6c6f400 0 raw
> + receive list 'rx_fil':
> (any: no entry)
> + device can_id can_mask matches sock_inode function
> + vcan0 80000123 c00007ff 0 000000000000f862 raw_rcv [can_raw]
^^^^^ ^ ^^^
| | |
| / do we want to align "sock_inode" to the right?
| /
| do we want to align "can_id" to the right?
|
do we want to take care of max length of interfaces of
IFNAMSIZ == 16?
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung Nürnberg | Phone: +49-5121-206917-129 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-9 |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-08-26 11:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-15 10:34 [can-next v2] can: proc: remove pointers from CAN specific proc output Oliver Hartkopp
2026-08-20 14:27 ` Sebastian Andrzej Siewior
2026-08-26 11:28 ` Marc Kleine-Budde [this message]
2026-08-26 19:25 ` Oliver Hartkopp
-- strict thread matches above, loose matches on Subject: below --
2026-10-12 11:58 Oliver Hartkopp
2026-10-12 12:21 ` Marc Kleine-Budde
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=20260826-soft-python-of-charisma-e981f4-mkl@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=bigeasy@linutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=socketcan@hartkopp.net \
/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