From: Petr Machata <petrm@nvidia.com>
To: Daniel Machon <daniel.machon@microchip.com>
Cc: <netdev@vger.kernel.org>, <davem@davemloft.net>,
<petrm@nvidia.com>, <maxime.chevallier@bootlin.com>,
<thomas.petazzoni@bootlin.com>, <edumazet@google.com>,
<kuba@kernel.org>, <pabeni@redhat.com>,
<lars.povlsen@microchip.com>, <Steen.Hegelund@microchip.com>,
<UNGLinuxDriver@microchip.com>, <joe@perches.com>,
<linux@armlinux.org.uk>, <horatiu.vultur@microchip.com>,
<Julia.Lawall@inria.fr>, <vladimir.oltean@nxp.com>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH net-next v5 0/6] Add new PCP and APPTRUST attributes to dcbnl
Date: Mon, 31 Oct 2022 17:02:27 +0100 [thread overview]
Message-ID: <87y1swugk6.fsf@nvidia.com> (raw)
In-Reply-To: <20221028131403.1055694-1-daniel.machon@microchip.com>
I believe my comments from v4 still apply to this version.
prev parent reply other threads:[~2022-10-31 16:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 13:13 [PATCH net-next v5 0/6] Add new PCP and APPTRUST attributes to dcbnl Daniel Machon
2022-10-28 13:13 ` [PATCH net-next v5 1/6] net: dcb: add new pcp selector to app object Daniel Machon
2022-10-28 13:13 ` [PATCH net-next v5 2/6] net: dcb: add new apptrust attribute Daniel Machon
2022-10-31 10:40 ` Steen Hegelund
2022-10-31 13:45 ` Daniel.Machon
2022-10-28 13:14 ` [PATCH net-next v5 3/6] net: microchip: sparx5: add support for offloading pcp table Daniel Machon
2022-10-28 13:14 ` [PATCH net-next v5 4/6] net: microchip: sparx5: add support for apptrust Daniel Machon
2022-10-28 13:14 ` [PATCH net-next v5 5/6] net: microchip: sparx5: add support for offloading dscp table Daniel Machon
2022-10-28 13:14 ` [PATCH net-next v5 6/6] net: microchip: sparx5: add support for offloading default prio Daniel Machon
2022-10-31 16:02 ` Petr Machata [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=87y1swugk6.fsf@nvidia.com \
--to=petrm@nvidia.com \
--cc=Julia.Lawall@inria.fr \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=daniel.machon@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horatiu.vultur@microchip.com \
--cc=joe@perches.com \
--cc=kuba@kernel.org \
--cc=lars.povlsen@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=vladimir.oltean@nxp.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).