Linux Documentation
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Karl Mehltretter <kmehltretter@gmail.com>,
	Jeremy Kerr <jk@codeconstruct.com.au>,
	Matt Johnston <matt@codeconstruct.com.au>
Cc: netdev@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
	linux-doc@vger.kernel.org, Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH net-next] docs: mctp: Fix the struct net_device name
Date: Sat, 5 Sep 2026 21:22:00 -0700	[thread overview]
Message-ID: <f63c002a-39ce-490f-9a7b-4f6baa8147b6@infradead.org> (raw)
In-Reply-To: <20260905095116.42147-1-kmehltretter@gmail.com>



On 9/5/26 2:51 AM, Karl Mehltretter wrote:
> struct netdevice does not exist; the type is struct net_device.
> 
> Use it.
> 
> Fixes: 6a2d98b18900 ("mctp: Add MCTP overview document")
> Assisted-by: LLM
> Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>

Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.

> ---
>  Documentation/networking/mctp.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/networking/mctp.rst b/Documentation/networking/mctp.rst
> index c628cb5406d2..3bff00c11702 100644
> --- a/Documentation/networking/mctp.rst
> +++ b/Documentation/networking/mctp.rst
> @@ -19,7 +19,7 @@ networks.
>  
>  An interface (or "link") is an instance of an MCTP physical transport binding
>  (as defined by DSP0236, section 3.2.47), likely connected to a specific hardware
> -device. This is represented as a ``struct netdevice``.
> +device. This is represented as a ``struct net_device``.
>  
>  A network defines a unique address space for MCTP endpoints by endpoint-ID
>  (described by DSP0236, section 3.2.31). A network has a user-visible identifier

-- 
~Randy

  reply	other threads:[~2026-09-06  4:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-05  9:51 [PATCH net-next] docs: mctp: Fix the struct net_device name Karl Mehltretter
2026-09-06  4:22 ` Randy Dunlap [this message]
2026-09-10  1:10 ` patchwork-bot+netdevbpf

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=f63c002a-39ce-490f-9a7b-4f6baa8147b6@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=corbet@lwn.net \
    --cc=jk@codeconstruct.com.au \
    --cc=kmehltretter@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=matt@codeconstruct.com.au \
    --cc=netdev@vger.kernel.org \
    --cc=skhan@linuxfoundation.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