All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Machata <petrm@nvidia.com>
To: Daniel Machon <daniel.machon@microchip.com>
Cc: <netdev@vger.kernel.org>, <Allan.Nielsen@microchip.com>,
	<UNGLinuxDriver@microchip.com>, <maxime.chevallier@bootlin.com>,
	<vladimir.oltean@nxp.com>, <petrm@nvidia.com>, <kuba@kernel.org>,
	<vinicius.gomes@intel.com>, <thomas.petazzoni@bootlin.com>
Subject: Re: [RFC PATCH v2 net-next 0/2] Add PCP selector and new APPTRUST attribute
Date: Mon, 19 Sep 2022 09:54:23 +0200	[thread overview]
Message-ID: <87illjyeui.fsf@nvidia.com> (raw)
In-Reply-To: <20220915095757.2861822-1-daniel.machon@microchip.com>

Thanks, this looks good to me overall, despite the several points
Vladimir and I raised. I think it would be good to send this as non-RFC.

Note that for the non-RFC version, an actual user of the interface needs
to be present as well. So one of the offloading drivers should be
adapted to make use of the APP_TRUST and the new PCP selector.
mlxsw would like to make use of both, but I don't know when I will have
time to implement that.

  parent reply	other threads:[~2022-09-19  8:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-15  9:57 [RFC PATCH v2 net-next 0/2] Add PCP selector and new APPTRUST attribute Daniel Machon
2022-09-15  9:57 ` [RFC PATCH v2 net-next 1/2] net: dcb: add new pcp selector to app object Daniel Machon
2022-09-19  9:45   ` Petr Machata
2022-09-28 13:52     ` Daniel.Machon
2022-09-28 15:50       ` Petr Machata
2022-09-15  9:57 ` [RFC PATCH v2 net-next 2/2] net: dcb: add new apptrust attribute Daniel Machon
2022-09-15  9:51   ` Vladimir Oltean
2022-09-19  7:30   ` Petr Machata
2022-09-19  7:54 ` Petr Machata [this message]
2022-09-19  8:13   ` [RFC PATCH v2 net-next 0/2] Add PCP selector and new APPTRUST attribute Daniel.Machon
2022-09-19 15:11     ` Petr Machata

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=87illjyeui.fsf@nvidia.com \
    --to=petrm@nvidia.com \
    --cc=Allan.Nielsen@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=daniel.machon@microchip.com \
    --cc=kuba@kernel.org \
    --cc=maxime.chevallier@bootlin.com \
    --cc=netdev@vger.kernel.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=vinicius.gomes@intel.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 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.