netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: emil.s.tantilov@intel.com
Cc: sri@us.ibm.com, herbert@gondor.apana.org.au, mst@redhat.com,
	netdev@vger.kernel.org
Subject: Re: [PATCH v2 net-next-2.6] packet: Add GSO/csum offload support.
Date: Fri, 05 Feb 2010 16:27:08 -0800 (PST)	[thread overview]
Message-ID: <20100205.162708.238568829.davem@davemloft.net> (raw)
In-Reply-To: <EA929A9653AAE14F841771FB1DE5A1365FDFE68A89@rrsmsx501.amr.corp.intel.com>

From: "Tantilov, Emil S" <emil.s.tantilov@intel.com>
Date: Fri, 5 Feb 2010 17:20:12 -0700

> I am seeing a build failure on one of my systems that has kernel with CONFIG_PACKET_MMAP disabled, which appears to be caused by this patch:
> 
> net/packet/af_packet.c: In function 'packet_setsockopt':
> net/packet/af_packet.c:1977: error: 'struct packet_sock' has no member named 'rx_ring'
> net/packet/af_packet.c:1977: error: 'struct packet_sock' has no member named 'tx_ring'

Thanks for the report.

This is a pretty essential part of AF_PACKET support that
what I'm going to do is simply remove this config option
in net-next-2.6 to fix this problem.

Thanks again.

      reply	other threads:[~2010-02-06  0:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-03 23:22 [PATCH v2 net-next-2.6] packet: Add GSO/csum offload support Sridhar Samudrala
2010-02-04 23:49 ` David Miller
2010-02-05  0:08 ` Herbert Xu
2010-02-05  0:17   ` Sridhar Samudrala
2010-02-05  0:53     ` Herbert Xu
2010-02-05  0:52 ` Herbert Xu
2010-02-05  1:02   ` Sridhar Samudrala
2010-02-05  2:14     ` Herbert Xu
2010-02-05  4:25       ` David Miller
2010-02-06  0:20 ` Tantilov, Emil S
2010-02-06  0:27   ` David Miller [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=20100205.162708.238568829.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=emil.s.tantilov@intel.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=sri@us.ibm.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).