netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: dborkman@redhat.com
Cc: netdev@vger.kernel.org, brouer@redhat.com
Subject: Re: [PATCH net-next 0/3] PF_PACKET updates
Date: Mon, 09 Dec 2013 20:24:05 -0500 (EST)	[thread overview]
Message-ID: <20131209.202405.918440581801459446.davem@davemloft.net> (raw)
In-Reply-To: <1386326177-4483-1-git-send-email-dborkman@redhat.com>

From: Daniel Borkmann <dborkman@redhat.com>
Date: Fri,  6 Dec 2013 11:36:14 +0100

> Patch descriptions in individual patches.
> 
> In order to avoid a possible merge conflict, we suggest to take
> the first patch through net tree, merge net into net-next and
> apply the remaining two patches on top of it. Dave, please let
> us know if you like to handle this differently than suggested.
> 
> For patch 3 we'll send a man-page update as a follow-up.

Patch #1 applied to 'net' and queued up for -stable.

Patch #2 and #3 applied to 'net-next'.

Thanks!

  parent reply	other threads:[~2013-12-10  1:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-06 10:36 [PATCH net-next 0/3] PF_PACKET updates Daniel Borkmann
2013-12-06 10:36 ` [PATCH net-next 1/3] packet: fix send path when running with proto == 0 Daniel Borkmann
2013-12-06 10:36 ` [PATCH net-next 2/3] net: dev: move inline skb_needs_linearize helper to header Daniel Borkmann
2013-12-06 10:36 ` [PATCH net-next 3/3] packet: introduce PACKET_QDISC_BYPASS socket option Daniel Borkmann
2013-12-10  1:24 ` David Miller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-01-12 16:22 [PATCH net-next 0/3] pf_packet updates Daniel Borkmann
2013-08-28 20:13 Daniel Borkmann
2013-08-29  5:39 ` David Miller
2013-08-29  6:20   ` Daniel Borkmann
2013-08-29 20:43     ` David Miller
2013-08-29 10:25   ` Eric Dumazet
2013-08-29 16:53     ` 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=20131209.202405.918440581801459446.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=brouer@redhat.com \
    --cc=dborkman@redhat.com \
    --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).