All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	wireless <linux-wireless@vger.kernel.org>
Subject: Re: Build error in 2.6.31-rc1-wl
Date: Thu, 2 Jul 2009 08:47:38 -0400	[thread overview]
Message-ID: <20090702124737.GA2839@tuxdriver.com> (raw)
In-Reply-To: <4A4BCA87.8020805@lwfinger.net>

On Wed, Jul 01, 2009 at 03:43:51PM -0500, Larry Finger wrote:
> When building the above kernel based on a fress pull of
> wireless-testing, I get the following build error:
> 
>   CC      net/core/skbuff.o
> net/core/skbuff.c: In function ‘__copy_skb_header’:
> net/core/skbuff.c:563: error: ‘struct sk_buff’ has no member named
> ‘do_not_encrypt’
> net/core/skbuff.c:563: error: ‘const struct sk_buff’ has no member
> named ‘do_not_encrypt’
> make[2]: *** [net/core/skbuff.o] Error 1
> 
> The code that errors is
> 
>         new->vlan_tci           = old->vlan_tci;
> #if defined(CONFIG_MAC80211) || defined(CONFIG_MAC80211_MODULE)
>         new->do_not_encrypt     = old->do_not_encrypt;
> #endif
> 
>         skb_copy_secmark(new, old);
> }

Some patch damage when moving to 2.6.31-rc1.  Johannes sent me a
fix-up yesterday, so I have folded it back into the damaged patch
and pushed it out.

Thanks,

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.
			¡Viva Honduras Libre!

      reply	other threads:[~2009-07-02 13:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-01 20:43 Build error in 2.6.31-rc1-wl Larry Finger
2009-07-02 12:47 ` John W. Linville [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=20090702124737.GA2839@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@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 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.