From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Heikki Krogerus <heikki.krogerus@linux.intel.com>
Subject: Re: linux-next: build failure after merge of the final tree (tty tree related)
Date: Fri, 27 Sep 2013 18:04:24 -0700 [thread overview]
Message-ID: <20130928010424.GB22939@kroah.com> (raw)
In-Reply-To: <20130927182117.42cdf5287fa1e9b40dd3f8e9@canb.auug.org.au>
On Fri, Sep 27, 2013 at 06:21:17PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the final tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> drivers/tty/serial/8250/8250_dw.c: In function 'dw8250_probe':
> drivers/tty/serial/8250/8250_dw.c:341:3: error: too many arguments to function 'dw8250_probe_acpi'
> err = dw8250_probe_acpi(&uart, data);
> ^
> drivers/tty/serial/8250/8250_dw.c:281:19: note: declared here
> static inline int dw8250_probe_acpi(struct uart_8250_port *up)
> ^
>
> Caused by commit fe95855539fd ("serial: 8250_dw: don't limit DMA support
> to ACPI") from the tty tree.
>
> I have reverted that commit for today (and commit 7fb8c56c7fa0 ("serial:
> 8250_dw: provide a filter for DMA channel detection") that depends on it).
Should now be fixed, thanks.
greg k-h
next prev parent reply other threads:[~2013-09-28 1:04 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 8:21 linux-next: build failure after merge of the final tree (tty tree related) Stephen Rothwell
2013-09-28 1:04 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-10-28 14:33 Stephen Rothwell
2013-10-28 14:33 ` Stephen Rothwell
2013-10-28 14:49 ` Michal Simek
2013-10-28 16:05 ` Sören Brinkmann
2013-10-28 16:05 ` Sören Brinkmann
2013-10-28 16:33 ` Greg KH
2013-10-29 7:04 ` Stephen Rothwell
2013-04-02 7:57 Stephen Rothwell
2012-11-26 13:49 Stephen Rothwell
2012-11-26 14:35 ` Steven Rostedt
2012-11-26 23:05 ` Stephen Rothwell
2012-12-13 23:32 ` Stephen Rothwell
2012-12-13 23:38 ` Greg KH
2012-12-14 0:11 ` Steven Rostedt
2012-09-24 14:36 Stephen Rothwell
2012-09-25 22:41 ` Greg KH
2012-07-20 5:02 Stephen Rothwell
2012-07-25 22:47 ` Greg KH
2012-07-26 0:23 ` Alan Cox
2012-07-25 22:52 ` Stephen Rothwell
2011-08-25 6:18 Stephen Rothwell
2011-08-25 6:18 ` Stephen Rothwell
2011-08-25 14:08 ` Greg KH
2011-08-25 14:08 ` Greg KH
2011-08-25 14:28 ` Timur Tabi
2011-08-25 14:28 ` Timur Tabi
2011-08-25 15:22 ` Timur Tabi
2011-08-25 15:22 ` Timur Tabi
2011-08-25 15:22 ` Timur Tabi
2011-08-25 15:51 ` Stephen Rothwell
2011-08-25 15:51 ` Stephen Rothwell
2011-08-25 15:51 ` Stephen Rothwell
2011-08-25 16:09 ` Arnaud Lacombe
2011-08-25 16:09 ` Arnaud Lacombe
2011-08-26 0:39 ` Stephen Rothwell
2011-08-26 0:39 ` Stephen Rothwell
2011-08-26 15:47 ` Arnaud Lacombe
2011-09-11 4:23 ` Stephen Rothwell
2011-09-11 9:05 ` Geert Uytterhoeven
2010-12-17 6:11 Stephen Rothwell
2010-12-17 7:04 ` Greg KH
2010-12-17 10:16 ` Thomas Gleixner
2011-01-06 3:27 ` Stephen Rothwell
2011-01-06 18:45 ` Greg KH
2010-11-12 1:57 Stephen Rothwell
2010-11-12 10:44 ` Alan Cox
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=20130928010424.GB22939@kroah.com \
--to=greg@kroah.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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.