archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <>
To: Stephen Rothwell <>
	Scott Feldman <>,
	"David S. Miller" <>
Subject: Re: linux-next: Tree for May 13 (avr32 build error due to switchdev patch)
Date: Wed, 13 May 2015 17:24:34 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Wed, May 13, 2015 at 06:09:27PM +1000, Stephen Rothwell wrote:
> Hi all,
> Changes since 20150512:
> New tree: h8300
> The net-next tree gained a conflict against the net tree.
> The security tree gained conflicts against the vfs tree.
> The spi tree lost its build failure.
> The target-updates tree still had its build failure so I used the version
> from next-20150511.
> The gpio tree gained a build failure so I used the version from
> next-20150512.
> Non-merge commits (relative to Linus' tree): 3825
>  3592 files changed, 173394 insertions(+), 76013 deletions(-)
> ----------------------------------------------------------------------------

net/bridge/br_stp.c: In function 'br_set_state':
net/bridge/br_stp.c:44: error: unknown field 'stp_state' specified in initializer

The problem is most likely that the variable is part of an unnamed union, and
it looks like gcc 4.2.4 doesn't understand that. avr32 is not supported by more
recent versions of gcc, so I can not update the toolchain to work around the

Introduced by commit 3563606258cf3 ("switchdev: convert STP update to switchdev
attr set").


      reply	other threads:[~2015-05-14  0:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-13  8:09 linux-next: Tree for May 13 Stephen Rothwell
2015-05-14  0:24 ` Guenter Roeck [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* 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).