From: Jakub Kicinski <kuba@kernel.org>
To: Jiri Pirko <jiri@resnulli.us>
Cc: Shay Drory <shayd@nvidia.com>,
netdev@vger.kernel.org, davem@davemloft.net, danielj@nvidia.com,
yishaih@nvidia.com, jiri@nvidia.com, saeedm@nvidia.com,
parav@nvidia.com
Subject: Re: [PATCH net-next V2 7/8] devlink: Expose port function commands to control migratable
Date: Fri, 2 Dec 2022 10:39:48 -0800 [thread overview]
Message-ID: <20221202103948.714a0db4@kernel.org> (raw)
In-Reply-To: <Y4m/M+jeF+CBqTyW@nanopsycho>
On Fri, 2 Dec 2022 10:02:43 +0100 Jiri Pirko wrote:
> I believe that you put reported by only to patches that fix the reported
> issue which exists in-tree. It does not apply to issues found on
> a submitted patch.
+1, I also find adding the tag for previous-revision-issues
misleading
next prev parent reply other threads:[~2022-12-02 18:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 8:26 [PATCH net-next V2 0/8] devlink: Add port function attribute to enable/disable Roce and migratable Shay Drory
2022-12-02 8:26 ` [PATCH net-next V2 1/8] net/mlx5: Introduce IFC bits for migratable Shay Drory
2022-12-02 8:26 ` [PATCH net-next V2 2/8] devlink: Validate port function request Shay Drory
2022-12-02 18:42 ` Jakub Kicinski
2022-12-02 8:26 ` [PATCH net-next V2 3/8] devlink: Move devlink port function hw_addr attr documentation Shay Drory
2022-12-02 8:26 ` [PATCH net-next V2 4/8] devlink: Expose port function commands to control RoCE Shay Drory
2022-12-02 18:56 ` Jakub Kicinski
2022-12-02 8:26 ` [PATCH net-next V2 5/8] net/mlx5: Add generic getters for other functions caps Shay Drory
2022-12-02 8:26 ` [PATCH net-next V2 6/8] net/mlx5: E-Switch, Implement devlink port function cmds to control RoCE Shay Drory
2022-12-02 8:26 ` [PATCH net-next V2 7/8] devlink: Expose port function commands to control migratable Shay Drory
2022-12-02 9:02 ` Jiri Pirko
2022-12-02 18:39 ` Jakub Kicinski [this message]
2022-12-04 9:31 ` Shay Drory
2022-12-02 17:26 ` kernel test robot
2022-12-02 18:58 ` Jakub Kicinski
2022-12-02 8:26 ` [PATCH net-next V2 8/8] net/mlx5: E-Switch, Implement devlink port function cmds " Shay Drory
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=20221202103948.714a0db4@kernel.org \
--to=kuba@kernel.org \
--cc=danielj@nvidia.com \
--cc=davem@davemloft.net \
--cc=jiri@nvidia.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=parav@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=shayd@nvidia.com \
--cc=yishaih@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 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.