[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGHK07D_XCpU6V6oJ2rhR1=rX5P6t8ZhTMT7GEAyrBXoc=hbcQ@mail.gmail.com>
Date: Wed, 18 Jul 2018 11:55:51 +1000
From: Jonathan Maxwell <jmaxwell37@...il.com>
To: Eric Dumazet <eric.dumazet@...il.com>
Cc: David Miller <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Neal Cardwell <ncardwell@...gle.com>,
David Laight <David.Laight@...lab.com>,
kuznet <kuznet@....inr.ac.ru>,
yoshfuji <yoshfuji@...ux-ipv6.org>,
Netdev <netdev@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Jon Maxwell <jmaxwell@...hat.com>
Subject: Re: [PATCH net-next 0/3] tcp: improve setsockopt() TCP_USER_TIMEOUT accuracy
After committing the patches in my net-next git branch I used git send-mail:
git send-email --identity=XXX --cover-letter --annotate origin
--compose --signoff
and manually updated it based on an example of yours:
https://lwn.net/Articles/706491/
I can see the 3 patches that I just submitted on:
https://patchwork.ozlabs.org/project/netdev/list/
Flagged as under review by DaveM.
On Wed, Jul 18, 2018 at 11:20 AM, Eric Dumazet <eric.dumazet@...il.com> wrote:
>
>
> On 07/17/2018 05:46 PM, Jon Maxwell wrote:
>> Based on:
>>
>> https://patchwork.kernel.org/patch/10516195/
>>
>
> I must confess I am lost with your submissions.
>
> Patchwork is also lost ( https://patchwork.ozlabs.org/project/netdev/list/ )
>
> Are you really using git format-patch ?
>
> Normally all the patches should have a common [PATCH Vx net-next] string
>
> git format-patch -o ../output --cover-letter --subject-prefix "PATCH V3 net-next" HEAD~3
>
>
Powered by blists - more mailing lists