netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vlad Yasevich <vyasevic@redhat.com>
To: David Miller <davem@davemloft.net>, vyasevich@gmail.com
Cc: eric.dumazet@gmail.com, mst@redhat.com, netdev@vger.kernel.org,
	virtualization@lists.linux-foundation.org,
	hannes@stressinduktion.org, ben@decadent.org.uk
Subject: Re: [PATCH v2 0/3] Restore UFO support to virtio_net devices
Date: Mon, 02 Feb 2015 10:04:09 -0500	[thread overview]
Message-ID: <54CF91E9.5040108@redhat.com> (raw)
In-Reply-To: <20150201.222834.1543634857152757099.davem@davemloft.net>

On 02/02/2015 01:28 AM, David Miller wrote:
> From: David Miller <davem@davemloft.net>
> Date: Sun, 01 Feb 2015 22:19:35 -0800 (PST)
> 
>> Series applied and queued up for -stable.
> 
> I have to revert, this breaks the build.
> 
> net/built-in.o: In function `udp6_ufo_fragment':
> udp_offload.c:(.text+0x103380): undefined reference to `ipv6_select_ident'
> 

Sorry, Dave.  I am not sure what happened since the patches in my branch build
and boot.

In any case just to make sure, I've rebased on the latest net, rebuilt and reposted
the series.

Thanks
-vlad

      reply	other threads:[~2015-02-02 15:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-30 19:27 [PATCH v2 0/3] Restore UFO support to virtio_net devices Vladislav Yasevich
2015-01-30 19:27 ` [PATCH v2 1/3] ipv6: Select fragment id during UFO segmentation if not set Vladislav Yasevich
2015-01-31 17:11   ` Michael S. Tsirkin
2015-01-30 19:27 ` [PATCH v2 2/3] Revert "drivers/net, ipv6: Select IPv6 fragment idents for virtio UFO packets" Vladislav Yasevich
2015-01-31 17:11   ` Michael S. Tsirkin
2015-01-30 19:27 ` [PATCH v2 3/3] Revert "drivers/net: Disable UFO through virtio" Vladislav Yasevich
2015-01-31 17:11   ` Michael S. Tsirkin
2015-01-31 17:17 ` [PATCH v2 0/3] Restore UFO support to virtio_net devices Michael S. Tsirkin
2015-02-02  6:19 ` David Miller
2015-02-02  6:28   ` David Miller
2015-02-02 15:04     ` Vlad Yasevich [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=54CF91E9.5040108@redhat.com \
    --to=vyasevic@redhat.com \
    --cc=ben@decadent.org.uk \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=hannes@stressinduktion.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=vyasevich@gmail.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).