Re: [PATCH net-next 0/3] tcp: improve setsockopt() TCP_USER_TIMEOUT accuracy

Okay I see what you mean looking some examples on:

https://patchwork.ozlabs.org/project/netdev/list/

I'll resubmit with the correct patch series numbers but with
the same detailed description.

On Wed, Jul 18, 2018 at 12:40 PM, Eric Dumazet [off-list ref] wrote:

On 07/17/2018 06:55 PM, Jonathan Maxwell wrote:

quoted

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.

I dunno, each patch belongs to a separate patch series, this is not expected.

Compare to what happens on https://patchwork.ozlabs.org/project/netdev/list/  for a proper submission.

If you click on https://patchwork.ozlabs.org/project/netdev/list/?series=56100  for example,
you can see 5 patch in a series.

Standard workflow :

git-format-patch ...

<edit cover letter>

git send-email --to "David S. Miller [off-list ref]" \
        --cc "netdev [off-list ref]" \
        --cc "Eric Dumazet [off-list ref]" \
        00*