From: Jakub Kicinski <kuba@kernel.org>
To: Taehee Yoo <ap420073@gmail.com>
Cc: davem@davemloft.net, pabeni@redhat.com, netdev@vger.kernel.org,
irusskikh@marvell.com, ast@kernel.org, daniel@iogearbox.net,
hawk@kernel.org, john.fastabend@gmail.com, andrii@kernel.org,
kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
kpsingh@kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/3] net: atlantic: Add XDP support
Date: Fri, 8 Apr 2022 11:58:25 -0700 [thread overview]
Message-ID: <20220408115825.319e815e@kernel.org> (raw)
In-Reply-To: <d4106b81-31cb-2569-6b49-9393bd2c2b34@gmail.com>
On Sat, 9 Apr 2022 02:32:51 +0900 Taehee Yoo wrote:
> I will send v4 patch because of compile warning.
Please don't resend your series more often than once a day.
If your code doesn't compile cleanly, too bad, you'll have to wait.
This is sort of documented in the FAQ:
2.10. I have received review feedback, when should I post a revised
version of the patches?
Allow at least 24 hours to pass between postings. This will
ensure reviewers from all geographical locations have a chance
to chime in. Do not wait too long (weeks) between postings
either as it will make it harder for reviewers to recall all
the context.
https://www.kernel.org/doc/html/latest/process/maintainer-netdev.html#i-have-received-review-feedback-when-should-i-post-a-revised-version-of-the-patches
next prev parent reply other threads:[~2022-04-08 18:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 16:59 [PATCH net-next v3 0/3] net: atlantic: Add XDP support Taehee Yoo
2022-04-08 16:59 ` [PATCH net-next v3 1/3] net: atlantic: Implement xdp control plane Taehee Yoo
2022-04-08 16:59 ` [PATCH net-next v3 2/3] net: atlantic: Implement xdp data plane Taehee Yoo
2022-04-08 16:59 ` [PATCH net-next v3 3/3] net: atlantic: Implement .ndo_xdp_xmit handler Taehee Yoo
2022-04-08 17:32 ` [PATCH net-next v3 0/3] net: atlantic: Add XDP support Taehee Yoo
2022-04-08 18:58 ` Jakub Kicinski [this message]
2022-04-08 19:49 ` Taehee Yoo
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=20220408115825.319e815e@kernel.org \
--to=kuba@kernel.org \
--cc=andrii@kernel.org \
--cc=ap420073@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=hawk@kernel.org \
--cc=irusskikh@marvell.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=songliubraving@fb.com \
--cc=yhs@fb.com \
/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).