linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <srostedt@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	"H. Peter Anvin" <hpa@zytor.com>,
	linux-next@vger.kernel.org,
	"Luis R. Rodriguez" <lrodriguez@atheros.com>,
	"John W. Linville" <linville@tuxdriver.com>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: linux-next: ftrace tree build failure
Date: Mon, 24 Nov 2008 22:21:38 -0500	[thread overview]
Message-ID: <1227583298.7622.9.camel@localhost.localdomain> (raw)
In-Reply-To: <20081125140719.03a8cdfb.sfr@canb.auug.org.au>


On Tue, 2008-11-25 at 14:07 +1100, Stephen Rothwell wrote:
> Hi all,
> 
> Today's linux-next build (x86_64 allmodconfig) failed like this:
> 
> net/wireless/reg.c:348:29: error: macro "if" passed 2 arguments, but takes just 1
> net/wireless/reg.c: In function 'ignore_request':
> net/wireless/reg.c:349: error: expected '(' before 'return'
> 
> This is clearly a bug in in the above file and should be fixed there, so
> I have applied the following patch for today.  I expect some patch to fix
> this to appear in the wireless-current or net-current tree very soon.
> 

Ingo already has this in his queue too.

http://marc.info/?l=linux-kernel&m=122745649425646&w=2

-- Steve

  reply	other threads:[~2008-11-25  3:22 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-25  3:07 linux-next: ftrace tree build failure Stephen Rothwell
2008-11-25  3:21 ` Steven Rostedt [this message]
2008-11-25  7:28 ` Ingo Molnar
2008-11-25  7:43   ` Stephen Rothwell
2008-11-25  8:04     ` Ingo Molnar
2008-11-25 14:57       ` John W. Linville
2008-11-25 18:46         ` Luis R. Rodriguez
2008-11-26  0:08           ` Stephen Rothwell
2008-11-26  0:14             ` Luis R. Rodriguez
  -- strict thread matches above, loose matches on Subject: below --
2009-01-07  0:53 Stephen Rothwell
2009-01-07  9:55 ` Ingo Molnar
2009-01-07 21:20   ` Stephen Rothwell
2009-01-02  9:07 Stephen Rothwell
2009-01-02  9:14 ` Ingo Molnar
2009-01-02 10:22   ` Stephen Rothwell
2009-01-02 11:16     ` Ingo Molnar
2008-11-25  3:21 Stephen Rothwell
2008-11-25  3:48 ` Steven Rostedt
2008-11-25  4:13   ` Stephen Rothwell
2008-11-25  4:31     ` Steven Rostedt
2008-11-25  5:09       ` Stephen Rothwell
2008-11-25  5:44         ` Steven Rostedt
2008-11-25  6:57           ` Stephen Rothwell
2008-11-25  7:14             ` Ingo Molnar
2008-11-25  7:26               ` Stephen Rothwell
2008-11-25  5:24     ` Steven Rostedt
2008-08-25  3:08 Stephen Rothwell
2008-08-25  6:05 ` Ingo Molnar
2008-08-25  6:11   ` Ingo Molnar
2008-08-25  6:31     ` Stephen Rothwell
2008-08-25  3:01 Stephen Rothwell
2008-08-25  6:09 ` Ingo Molnar
2008-08-25 16:42   ` Steven Rostedt
2008-08-25 16:46     ` Steven Rostedt
2008-08-15  2:27 Stephen Rothwell
2008-08-15  7:56 ` Ingo Molnar
2008-08-15  8:29   ` Stephen Rothwell

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=1227583298.7622.9.camel@localhost.localdomain \
    --to=srostedt@redhat.com \
    --cc=davem@davemloft.net \
    --cc=hpa@zytor.com \
    --cc=linux-next@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=lrodriguez@atheros.com \
    --cc=mingo@elte.hu \
    --cc=sfr@canb.auug.org.au \
    --cc=tglx@linutronix.de \
    /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).