[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220223180028.47f14132@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date: Wed, 23 Feb 2022 18:00:28 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Saeed Mahameed <saeedm@...dia.com>
Cc: Saeed Mahameed <saeed@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Jason Gunthorpe <jgg@...dia.com>,
Leon Romanovsky <leonro@...dia.com>,
linux-rdma@...r.kernel.org, netdev@...r.kernel.org,
Saeed Mahameed <saeedm@...lanox.com>
Subject: Re: [mlx5-next 13/17] net/mlx5: Use mlx5_cmd_do() in core
create_{cq,dct}
On Wed, 23 Feb 2022 15:57:02 -0800 Saeed Mahameed wrote:
> On 23 Feb 15:20, Jakub Kicinski wrote:
> >On Tue, 22 Feb 2022 21:09:28 -0800 Saeed Mahameed wrote:
> >> Signed-off-by: Saeed Mahameed <saeedm@...lanox.com>
> >> Signed-off-by: Saeed Mahameed <saeedm@...dia.com>
> >
> >nit: double-signed
>
> different emails, the patch was authored back then when i had the mellanox
> email, If I want to keep the original author email, then i must sign with both
> emails, once as author and once as submitter.
>
> The other option is to override the author email with the new email, but
> I don't like to mess around with history ;)..
Ack, just an FYI, don't think the bots will actually catch this case.
Powered by blists - more mailing lists