netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: dlinkin@nvidia.com, netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, jiri@nvidia.com,
	stephen@networkplumber.org, vladbu@nvidia.com, parav@nvidia.com,
	huyn@nvidia.com
Subject: Re: [PATCH RESEND iproute2 net-next 3/4] devlink: Add port func rate support
Date: Thu, 10 Jun 2021 20:52:59 -0600	[thread overview]
Message-ID: <503b179f-5831-46a3-f8f8-3271e3b796e6@gmail.com> (raw)
In-Reply-To: <1623151354-30930-4-git-send-email-dlinkin@nvidia.com>

This one needs to be rebased. Must be Parav's patch that created a conflict.

  reply	other threads:[~2021-06-11  2:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-08 11:22 [PATCH RESEND iproute2 net-next 0/4] devlink rate support dlinkin
2021-06-08 11:22 ` [PATCH RESEND iproute2 net-next 1/4] uapi: update devlink kernel header dlinkin
2021-06-08 11:22 ` [PATCH RESEND iproute2 net-next 2/4] devlink: Add helper function to validate object handler dlinkin
2021-06-08 11:22 ` [PATCH RESEND iproute2 net-next 3/4] devlink: Add port func rate support dlinkin
2021-06-11  2:52   ` David Ahern [this message]
2021-06-08 11:22 ` [PATCH RESEND iproute2 net-next 4/4] devlink: Add ISO/IEC switch dlinkin
  -- strict thread matches above, loose matches on Subject: below --
2021-06-02 12:17 [PATCH RESEND net-next v3 00/18] devlink: rate objects API dlinkin
2021-06-02 12:31 ` [PATCH RESEND iproute2 net-next 0/4] devlink rate support Dmytro Linkin
2021-06-02 12:31   ` [PATCH RESEND iproute2 net-next 3/4] devlink: Add port func " Dmytro Linkin

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=503b179f-5831-46a3-f8f8-3271e3b796e6@gmail.com \
    --to=dsahern@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dlinkin@nvidia.com \
    --cc=huyn@nvidia.com \
    --cc=jiri@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=parav@nvidia.com \
    --cc=stephen@networkplumber.org \
    --cc=vladbu@nvidia.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).