public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Kerr <jk@codeconstruct.com.au>
To: Badal Nilawar <badal.nilawar@intel.com>,
	dri-devel@lists.freedesktop.org,  intel-xe@lists.freedesktop.org,
	netdev@vger.kernel.org,  linux-kernel@vger.kernel.org
Cc: rodrigo.vivi@intel.com, wojciech.drewek@intel.com,
	michael.brooks@intel.com,  heikki.krogerus@intel.com,
	michael.j.ruhl@intel.com,  thomas.hellstrom@linux.intel.com,
	michal.winiarski@intel.com,  anshuman.gupta@intel.com,
	jacob.e.keller@intel.com,  maarten.lankhorst@linux.intel.com,
	matthew.brost@intel.com,  anthony.l.nguyen@intel.com,
	przemyslaw.kitszel@intel.com,  mika.westerberg@linux.intel.com,
	andriy.shevchenko@linux.intel.com,
	 singaravelan.nallasellan@intel.com, kelvin.gardiner@intel.com,
	 matt@codeconstruct.com.au, andrew+netdev@lunn.ch,
	davem@davemloft.net,  edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, james.ausmus@intel.com
Subject: Re: [RFC PATCH 0/1] Proposal for in-band firmware update over PLDM-MCTP
Date: Tue, 05 May 2026 10:15:31 +0800	[thread overview]
Message-ID: <9cee1c2102f53bb33e96c186c21ba6447d1db4cb.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20260504193420.1232842-3-badal.nilawar@intel.com>

Hi Badal,

Thanks for sending this RFC through! It's good to have some early input
on the structure here.

> Problem statement: 

This is exceptionally verbose for "we would like to add a MCTP transport
driver". :)

> Option 1: MCTP Transport as Part of drivers/gpu/drm/xe Subsystem

This sounds like the best approach to me. The MCTP transport drivers in
drivers/net/mctp are intended to be fairly hardware-agnostic, and all
are spec compliant. I see no issue with having your own code do a
mctp_register_netdev() from elsewhere in the tree.

I'll also reply on 1/1 with some implementation comments.

> Note: This RFC is prepared with AI assistance (e.g. GitHub Copilot etc).

Then please ensure you have read
Documentation/process/coding-assistants.rst, as you are missing the
Attribution requirements from that.

Cheers,


Jeremy

      parent reply	other threads:[~2026-05-05  2:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-04 19:34 [RFC PATCH 0/1] Proposal for in-band firmware update over PLDM-MCTP Badal Nilawar
2026-05-04 19:34 ` [RFC PATCH 1/1] xe/xe_mctp_mailbox: Add support for MCTP transport over mailbox Badal Nilawar
2026-05-05  2:15   ` Jeremy Kerr
2026-05-05  8:23   ` Andy Shevchenko
2026-05-05  2:15 ` Jeremy Kerr [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=9cee1c2102f53bb33e96c186c21ba6447d1db4cb.camel@codeconstruct.com.au \
    --to=jk@codeconstruct.com.au \
    --cc=andrew+netdev@lunn.ch \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=badal.nilawar@intel.com \
    --cc=davem@davemloft.net \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=edumazet@google.com \
    --cc=heikki.krogerus@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jacob.e.keller@intel.com \
    --cc=james.ausmus@intel.com \
    --cc=kelvin.gardiner@intel.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=matt@codeconstruct.com.au \
    --cc=matthew.brost@intel.com \
    --cc=michael.brooks@intel.com \
    --cc=michael.j.ruhl@intel.com \
    --cc=michal.winiarski@intel.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=singaravelan.nallasellan@intel.com \
    --cc=thomas.hellstrom@linux.intel.com \
    --cc=wojciech.drewek@intel.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