All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: al.drozdov@gmail.com
Cc: corbet@lwn.net, dborkman@redhat.com, edumazet@google.com,
	viro@zeniv.linux.org.uk, willemb@google.com, mst@redhat.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	tklauser@distanz.ch, linux-doc@vger.kernel.org,
	linux-api@vger.kernel.org
Subject: Re: [PATCH V2 2/2] af_packet: pass checksum validation status to the user
Date: Mon, 23 Mar 2015 22:01:43 -0400 (EDT)	[thread overview]
Message-ID: <20150323.220143.354611810286401972.davem@davemloft.net> (raw)
In-Reply-To: <1427091073-8129-2-git-send-email-al.drozdov@gmail.com>

From: Alexander Drozdov <al.drozdov@gmail.com>
Date: Mon, 23 Mar 2015 09:11:13 +0300

> Introduce TP_STATUS_CSUM_VALID tp_status flag to tell the
> af_packet user that at least the transport header checksum
> has been already validated.
> 
> For now, the flag may be set for incoming packets only.
> 
> Signed-off-by: Alexander Drozdov <al.drozdov@gmail.com>

Applied to net-next

  reply	other threads:[~2015-03-24  2:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-19  8:01 [PATCH 1/2] af_packet: make tpacket_rcv to not set status value before run_filter Alexander Drozdov
2015-03-19  8:01 ` [PATCH 2/2] af_packet: pass checksum validation status to the user Alexander Drozdov
2015-03-19 15:29   ` Willem de Bruijn
2015-03-19 18:08     ` Alexander Drozdov
2015-03-19 18:50       ` Willem de Bruijn
2015-03-20  6:46         ` Alexander Drozdov
2015-03-20 15:29           ` Willem de Bruijn
2015-03-23  6:11   ` [PATCH V2 1/2] af_packet: make tpacket_rcv to not set status value before run_filter Alexander Drozdov
2015-03-23  6:11     ` [PATCH V2 2/2] af_packet: pass checksum validation status to the user Alexander Drozdov
2015-03-24  2:01       ` David Miller [this message]
2015-03-24  2:01     ` [PATCH V2 1/2] af_packet: make tpacket_rcv to not set status value before run_filter David Miller

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=20150323.220143.354611810286401972.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=al.drozdov@gmail.com \
    --cc=corbet@lwn.net \
    --cc=dborkman@redhat.com \
    --cc=edumazet@google.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=tklauser@distanz.ch \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willemb@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.