All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: mkl@pengutronix.de, linux-can@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: of alloc_canxl_skb
Date: Fri, 13 Sep 2024 20:05:31 +0000	[thread overview]
Message-ID: <ZuSbC8iqeGcUnogC@gallifrey> (raw)
In-Reply-To: <2540406e-8da3-4cb8-bd1a-30271dd6cc67@hartkopp.net>

* Oliver Hartkopp (socketcan@hartkopp.net) wrote:
> Hi David,

Hi Oliver,

> On 13.09.24 16:03, Dr. David Alan Gilbert wrote:
> 
> >    I'm doing some deadcode hunting and noticed that
> > 
> >    alloc_canxl_skb in drivers/net/can/dev/skb.c
> > 
> > looks unused in the main kernel tree; is that expected?
> > I see it was added back in 2022 by
> >    fb08cba12b52 ("can: canxl: update CAN infrastructure for CAN XL frames")
> > 
> > I know almost exactly nothing about CAN, so I thought it best
> > to ask!
> 
> I created some slides so that you can get an introduction to the different
> CAN protocols CAN CC (aka Classical CAN), CAN FD and CAN XL:
> 
> https://github.com/linux-can/can-doc/tree/master/presentations

Thanks!

> The introduction of the CAN XL support lead to some clean up and rework also
> for the former alloc_can_skb() and alloc_canfd_skb() helpers.
> 
> The function is currently not in use in net/can/raw.c as it is only needed
> when a CAN XL frame is received from read hardware. But the patch also
> contains the definition of ETH_P_CANXL to already handle CAN XL frames
> properly inside the Linux kernel and e.g. for WireShark 4.4.
> 
> There are currently some CAN XL IP cores in development (see attached
> picture with an FPGA based IP core) and I am working on the kernel
> infrastructure (e.g. bitrate configuration enhancements) on this board. So
> alloc_canxl_skb() is already in use on my desk and there will be some more
> stuff showing up soon ;-)

OK, great - I won't try and deadcode it then!

Thanks again for the reply,

Dave


> Best regards,
> Oliver


-- 
 -----Open up your eyes, open up your mind, open up your code -------   
/ Dr. David Alan Gilbert    |       Running GNU/Linux       | Happy  \ 
\        dave @ treblig.org |                               | In Hex /
 \ _________________________|_____ http://www.treblig.org   |_______/

      reply	other threads:[~2024-09-13 20:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-13 14:03 of alloc_canxl_skb Dr. David Alan Gilbert
2024-09-13 19:51 ` Oliver Hartkopp
2024-09-13 20:05   ` Dr. David Alan Gilbert [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=ZuSbC8iqeGcUnogC@gallifrey \
    --to=linux@treblig.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --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 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.