[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20181212.164203.103708083863926865.davem@davemloft.net>
Date: Wed, 12 Dec 2018 16:42:03 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: saeedm@...lanox.com
Cc: yuehaibing@...wei.com, netdev@...r.kernel.org,
linux-rdma@...r.kernel.org, leon@...nel.org,
kernel-janitors@...r.kernel.org
Subject: Re: [PATCH net-next] net/mlx5: Remove duplicated include from
eswitch.c
From: Saeed Mahameed <saeedm@...lanox.com>
Date: Wed, 12 Dec 2018 20:27:59 +0000
> On Wed, 2018-12-12 at 10:55 -0800, David Miller wrote:
>> From: YueHaibing <yuehaibing@...wei.com>
>> Date: Wed, 12 Dec 2018 08:03:38 +0000
>>
>> > Remove duplicated include.
>> >
>> > Signed-off-by: YueHaibing <yuehaibing@...wei.com>
>>
>> Saeed, how would you like me to handle small fixes like this which
>> have been
>> explicitly ACK'd by a Mellanox developer?
>>
>> Do you want me to apply them directly or wait to get them from you in
>> your
>> next pull request?
>>
>
> Let's do the following, if I ACK them then you can apply them directly,
> otherwise i will notify and apply them to my branch and send them later
> to avoid any confusion or conflict with our shared branch.
>
> Does that work for you ? if not then you can always leave them to me.
That works for me, I'll apply directly only with your explicit ACK,
thanks Saeed.
Powered by blists - more mailing lists