From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751831AbbALDId (ORCPT ); Sun, 11 Jan 2015 22:08:33 -0500 Received: from shards.monkeyblade.net ([149.20.54.216]:43325 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750787AbbALDIb (ORCPT ); Sun, 11 Jan 2015 22:08:31 -0500 Date: Sun, 11 Jan 2015 22:08:29 -0500 (EST) Message-Id: <20150111.220829.865175509346236586.davem@davemloft.net> To: sfr@canb.auug.org.au Cc: netdev@vger.kernel.org, linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, xiyou.wangcong@gmail.com, vlee@twopensource.com Subject: Re: linux-next: build failure after merge of the net-next tree From: David Miller In-Reply-To: <20150112140515.369eb687@canb.auug.org.au> References: <20150112140515.369eb687@canb.auug.org.au> X-Mailer: Mew version 6.6 on Emacs 24.4 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.7 (shards.monkeyblade.net [149.20.54.216]); Sun, 11 Jan 2015 19:08:31 -0800 (PST) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Stephen Rothwell Date: Mon, 12 Jan 2015 14:05:15 +1100 > Hi all, > > After merging the net-next tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > Documentation/networking/timestamping/txtimestamp.c: In function '__recv_errmsg_cmsg': > Documentation/networking/timestamping/txtimestamp.c:205:33: error: dereferencing pointer to incomplete type > Documentation/networking/timestamping/txtimestamp.c:206:23: error: dereferencing pointer to incomplete type > > Caused by commit cd91cc5bdddf ("doc: fix the compile error of > txtimestamp.c"). On (at least) Debian stable, the system's definition > of struct in6_pktinfo depends on __USE_GNU being defined (at least, I > think that is the problem). > > I have reverted that commit for today. It's fixed as of 5 minutes ago in the net-next tree, sorry for this.