public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel•org>
To: Petr Machata <petrm@nvidia•com>
Cc: Daniel Machon <daniel.machon@microchip•com>,
	<netdev@vger•kernel.org>, <davem@davemloft•net>,
	<maxime.chevallier@bootlin•com>, <thomas.petazzoni@bootlin•com>,
	<edumazet@google•com>, <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 v2 1/6] net: dcb: add new pcp selector to app object
Date: Mon, 3 Oct 2022 09:25:22 -0700	[thread overview]
Message-ID: <20221003092522.6aaa6d55@kernel.org> (raw)
In-Reply-To: <87pmf9xrrd.fsf@nvidia.com>

On Mon, 3 Oct 2022 09:52:59 +0200 Petr Machata wrote:
> I assumed the policy is much more strict with changes like this. If you
> think it's OK, I'm fine with it as well.
> 
> The userspace (lldpad in particular) is doing the opposite thing BTW:
> assuming everything in the nest is a DCB_ATTR_IEEE_APP. When we start
> emitting the new attribute, it will get confused.

Can you add an attribute or a flag to the request which would turn
emitting the new attrs on?

  reply	other threads:[~2022-10-03 16:25 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-29 18:52 [PATCH net-next v2 0/6] Add new PCP and APPTRUST attributes to dcbnl Daniel Machon
2022-09-29 18:52 ` [PATCH net-next v2 1/6] net: dcb: add new pcp selector to app object Daniel Machon
2022-09-30 12:20   ` Petr Machata
2022-09-30 15:41     ` Petr Machata
2022-10-01  0:54     ` Jakub Kicinski
2022-10-03  7:52       ` Petr Machata
2022-10-03 16:25         ` Jakub Kicinski [this message]
2022-10-03 21:59           ` Daniel.Machon
2022-10-03 23:34             ` Jakub Kicinski
2022-10-04 10:56               ` Petr Machata
2022-10-04 10:20           ` Petr Machata
2022-10-04 10:52             ` Petr Machata
2022-10-04 19:51               ` Jakub Kicinski
2022-10-03  6:48     ` Daniel.Machon
2022-10-03  8:22       ` Petr Machata
2022-10-03  9:33         ` Daniel.Machon
2022-10-05 10:09           ` Petr Machata
2022-09-29 18:52 ` [PATCH net-next v2 2/6] net: dcb: add new apptrust attribute Daniel Machon
2022-09-30 13:03   ` Petr Machata
2022-09-29 18:52 ` [PATCH net-next v2 3/6] net: microchip: sparx5: add support for offloading pcp table Daniel Machon
2022-09-30 20:44   ` kernel test robot
2022-09-29 18:52 ` [PATCH net-next v2 4/6] net: microchip: sparx5: add support for apptrust Daniel Machon
2022-09-30 15:49   ` Petr Machata
2022-10-03  6:52     ` Daniel.Machon
2022-10-03  8:01       ` Petr Machata
2022-10-03  8:17         ` Daniel.Machon
2022-10-03  9:34           ` Petr Machata
2022-09-29 18:52 ` [PATCH net-next v2 5/6] net: microchip: sparx5: add support for offloading dscp table Daniel Machon
2022-09-30 23:23   ` kernel test robot
2022-09-29 18:52 ` [PATCH net-next v2 6/6] net: microchip: sparx5: add support for offloading default prio Daniel Machon

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=20221003092522.6aaa6d55@kernel.org \
    --to=kuba@kernel$(echo .)org \
    --cc=Julia.Lawall@inria$(echo .)fr \
    --cc=Steen.Hegelund@microchip$(echo .)com \
    --cc=UNGLinuxDriver@microchip$(echo .)com \
    --cc=daniel.machon@microchip$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=edumazet@google$(echo .)com \
    --cc=horatiu.vultur@microchip$(echo .)com \
    --cc=joe@perches$(echo .)com \
    --cc=lars.povlsen@microchip$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux@armlinux$(echo .)org.uk \
    --cc=maxime.chevallier@bootlin$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    --cc=petrm@nvidia$(echo .)com \
    --cc=thomas.petazzoni@bootlin$(echo .)com \
    --cc=vladimir.oltean@nxp$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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