From: Daniel Borkmann <daniel@iogearbox.net>
To: Mathias Kretschmer <mathias.kretschmer@fokus.fraunhofer.de>,
netdev@vger.kernel.org
Subject: Re: PATCH: af_packet / TX_RING not fully non-blocking (w/ MSG_DONTWAIT)
Date: Sun, 03 May 2015 23:39:30 +0200 [thread overview]
Message-ID: <55469592.6080305@iogearbox.net> (raw)
In-Reply-To: <5546065B.6080706@fokus.fraunhofer.de>
Hi Mathias,
On 05/03/2015 01:28 PM, Mathias Kretschmer wrote:
> Hi,
>
> following up on my initial post and the feedback I have received,
> please find attached/in-line an updated patch.
Yep, thanks for following up on this.
However, your submission (https://patchwork.ozlabs.org/patch/467377/)
format is not correct. Your email client corrupted the whitespace,
your Signed-off-by is missing, a proper commit description is missing
and which tree your patch is targeted at. I presume -net tree as it's
a fix.
You're best off sending this patch via git-send-email(1), see also
Documentation/SubmittingPatches from the kernel tree.
Taking a random example submission from patchwork, this is how the end
result could look like:
https://patchwork.ozlabs.org/patch/466743/
Thus, if you just write a proper commit message in git and use
git-format-patch(1) and git-send-email(1), you should be all set. Hope
that helps.
Cheers,
Daniel
> Changes:
> *) keep the unlikely() in the case sock_alloc_send_skb() fails, as here we enter the slow path, anyway.
> *) pass on the return code from sock_alloc_send_skb(), i.e. EGAIN
>
> Please consider this for inclusion.
>
> Cheers,
>
> Mathias
prev parent reply other threads:[~2015-05-03 21:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-03 11:28 PATCH: af_packet / TX_RING not fully non-blocking (w/ MSG_DONTWAIT) Mathias Kretschmer
2015-05-03 21:39 ` Daniel Borkmann [this message]
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=55469592.6080305@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=mathias.kretschmer@fokus.fraunhofer.de \
--cc=netdev@vger.kernel.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).