[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a8de53f1acb069057dedc94fb8bd29ea3e658716.camel@mellanox.com>
Date: Mon, 24 Jun 2019 21:57:05 +0000
From: Saeed Mahameed <saeedm@...lanox.com>
To: "leon@...nel.org" <leon@...nel.org>
CC: Jason Gunthorpe <jgg@...lanox.com>,
Yishai Hadas <yishaih@...lanox.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
"dledford@...hat.com" <dledford@...hat.com>
Subject: Re: [PATCH rdma-next v1 00/12] DEVX asynchronous events
On Wed, 2019-06-19 at 07:45 +0300, Leon Romanovsky wrote:
> On Tue, Jun 18, 2019 at 06:51:45PM +0000, Saeed Mahameed wrote:
> > On Tue, 2019-06-18 at 20:15 +0300, Leon Romanovsky wrote:
> > > From: Leon Romanovsky <leonro@...lanox.com>
> > >
> > > Changelog:
> > > v0 -> v1:
> >
> > Normally 1st submission is V1 and 2nd is V2.
> > so this should have been v1->v2.
>
> "Normally" depends on the language you are using. In C, everything
> starts from 0, including version of patches :).
>
You are wrong:
quoting: https://kernelnewbies.org/PatchTipsAndTricks
"For example, if you're sending the second revision of a patch, you
should use [PATCH v2]."
now don't tell me that second revision is actually 3rd revision or 1st
is 2nd :)..
> > For mlx5-next patches:
> >
> > Acked-by: Saeed Mahameed <saeedm@...lanox.com>
>
> Thanks
Powered by blists - more mailing lists