From: Eric Dumazet <eric.dumazet@gmail.com>
To: Jonathan Maxwell <jmaxwell37@gmail.com>,
Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Neal Cardwell <ncardwell@google.com>,
David Laight <David.Laight@aculab.com>,
kuznet <kuznet@ms2.inr.ac.ru>, yoshfuji <yoshfuji@linux-ipv6.org>,
Netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Jon Maxwell <jmaxwell@redhat.com>
Subject: Re: [PATCH net-next 0/3] tcp: improve setsockopt() TCP_USER_TIMEOUT accuracy
Date: Tue, 17 Jul 2018 19:40:34 -0700 [thread overview]
Message-ID: <4cd4429d-bca6-8b3d-1dd2-ef7f4cd102b7@gmail.com> (raw)
In-Reply-To: <CAGHK07D_XCpU6V6oJ2rhR1=rX5P6t8ZhTMT7GEAyrBXoc=hbcQ@mail.gmail.com>
On 07/17/2018 06:55 PM, Jonathan Maxwell wrote:
> 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 <davem@davemloft.net>" \
--cc "netdev <netdev@vger.kernel.org>" \
--cc "Eric Dumazet <edumazet@google.com>" \
00*
next prev parent reply other threads:[~2018-07-18 2:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 0:46 [PATCH net-next 0/3] tcp: improve setsockopt() TCP_USER_TIMEOUT accuracy Jon Maxwell
2018-07-18 1:20 ` Eric Dumazet
2018-07-18 1:55 ` Jonathan Maxwell
2018-07-18 2:40 ` Eric Dumazet [this message]
2018-07-18 2:57 ` Jonathan Maxwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4cd4429d-bca6-8b3d-1dd2-ef7f4cd102b7@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=David.Laight@aculab.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jmaxwell37@gmail.com \
--cc=jmaxwell@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).