From: Jakub Kicinski <kuba@kernel.org>
To: Konstantin Aladyshev <aladyshev22@gmail.com>
Cc: minyard@acm.org, joel@jms.id.au, andrew@aj.id.au,
avifishman70@gmail.com, tmaimon77@gmail.com,
tali.perry1@gmail.com, venture@google.com, yuenn@google.com,
benjaminfair@google.com, jk@codeconstruct.com.au,
matt@codeconstruct.com.au, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com,
openipmi-developer@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, openbmc@lists.ozlabs.org,
netdev@vger.kernel.org
Subject: Re: [PATCH v2 3/3] mctp: Add MCTP-over-KCS transport binding
Date: Mon, 2 Oct 2023 15:30:11 -0700 [thread overview]
Message-ID: <20231002153011.5444fd83@kernel.org> (raw)
In-Reply-To: <20231002143441.545-4-aladyshev22@gmail.com>
On Mon, 2 Oct 2023 17:34:41 +0300 Konstantin Aladyshev wrote:
> This change adds a MCTP KCS transport binding, as defined by the DMTF
> specificiation DSP0254 - "MCTP KCS Transport Binding".
> A MCTP protocol network device is created for each KCS channel found in
> the system.
> The interrupt code for the KCS state machine is based on the current
> IPMI KCS driver.
Still doesn't build, please make sure W=1 C=1 build is clean with both
GCC and Clang (you can point them at a specific path to avoid building
the entire kernel with the warnings enabled).
--
pw-bot: cr
next prev parent reply other threads:[~2023-10-02 22:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 14:34 [PATCH v2 0/3] Add MCTP-over-KCS transport binding Konstantin Aladyshev
2023-10-02 14:34 ` [PATCH v2 1/3] ipmi: Move KCS headers to common include folder Konstantin Aladyshev
2023-10-02 14:34 ` [PATCH v2 2/3] ipmi: Create header with KCS interface defines Konstantin Aladyshev
2023-10-02 14:34 ` [PATCH v2 3/3] mctp: Add MCTP-over-KCS transport binding Konstantin Aladyshev
2023-10-02 22:30 ` Jakub Kicinski [this message]
2023-10-02 23:04 ` kernel test robot
2023-10-03 13:21 ` Konstantin Aladyshev
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=20231002153011.5444fd83@kernel.org \
--to=kuba@kernel.org \
--cc=aladyshev22@gmail.com \
--cc=andrew@aj.id.au \
--cc=avifishman70@gmail.com \
--cc=benjaminfair@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jk@codeconstruct.com.au \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeconstruct.com.au \
--cc=minyard@acm.org \
--cc=netdev@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=pabeni@redhat.com \
--cc=tali.perry1@gmail.com \
--cc=tmaimon77@gmail.com \
--cc=venture@google.com \
--cc=yuenn@google.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).