All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Hurley <peter@hurleysoftware.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: linux-next: Tree for Nov 26 (staging/fwserial)
Date: Tue, 27 Nov 2012 02:17:30 -0500	[thread overview]
Message-ID: <1354000650.3284.9.camel@thor> (raw)
In-Reply-To: <50B3D767.70604@infradead.org>

On Mon, 2012-11-26 at 12:56 -0800, Randy Dunlap wrote:
> On 11/26/2012 06:17 AM, Stephen Rothwell wrote:
> 
> > Hi all,
> > 
> > Changes since 20121115:
> > 
> 
> 
> on i386:
> 
> drivers/staging/fwserial/dma_fifo.c: In function 'dma_fifo_in':
> drivers/staging/fwserial/dma_fifo.c:174:2: error: implicit declaration of function '__WARN_printf'

Apologies for the breakage. Not sure what possessed me to use an
internal macro so I could duplicate existing functionality...

Thanks for catching this now.

      parent reply	other threads:[~2012-11-27  7:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-26 14:17 linux-next: Tree for Nov 26 Stephen Rothwell
2012-11-26 14:17 ` Stephen Rothwell
2012-11-26 19:07 ` [PATCH -next] tty/serial: fix ifx6x60.c declaration warning Randy Dunlap
2012-11-26 19:43 ` linux-next: Tree for Nov 26 (mmc/host/tifm_sd.c) Randy Dunlap
2012-11-26 20:56 ` linux-next: Tree for Nov 26 (staging/fwserial) Randy Dunlap
2012-11-26 23:20   ` Andrew Morton
2012-11-27  7:39     ` Peter Hurley
2012-11-27  7:11   ` [PATCH -next] staging/fwserial: Fix build breakage when !CONFIG_BUG Peter Hurley
2012-11-27 18:42     ` Randy Dunlap
2012-11-28  0:56       ` Peter Hurley
2012-11-27  7:17   ` Peter Hurley [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=1354000650.3284.9.camel@thor \
    --to=peter@hurleysoftware.com \
    --cc=akpm@linux-foundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /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.