From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Greg KH <greg@kroah.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Chanho Min <chanho.min@lge.com>
Subject: linux-next: build failure after merge of the final tree (tty tree related)
Date: Tue, 2 Apr 2013 18:57:47 +1100 [thread overview]
Message-ID: <20130402185747.c4d8c60880025b242953da63@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1432 bytes --]
Hi all,
After merging the final tree, today's linux-next build (arm defconfig)
failed like this:
drivers/tty/serial/amba-pl011.c: In function 'pl011_rx_chars':
drivers/tty/serial/amba-pl011.c:1199:11: error: 'struct uart_amba_port' has no member named 'dmarx'
drivers/tty/serial/amba-pl011.c:1200:8: error: 'struct uart_amba_port' has no member named 'dmarx'
drivers/tty/serial/amba-pl011.c:1201:8: error: 'struct uart_amba_port' has no member named 'dmarx'
drivers/tty/serial/amba-pl011.c:1201:31: error: 'PL011_DMA_BUFFER_SIZE' undeclared (first use in this function)
drivers/tty/serial/amba-pl011.c:1201:31: note: each undeclared identifier is reported only once for each function it appears in
drivers/tty/serial/amba-pl011.c:1202:19: error: 'struct uart_amba_port' has no member named 'dmarx'
drivers/tty/serial/amba-pl011.c:1204:26: error: 'struct uart_amba_port' has no member named 'dmarx'
drivers/tty/serial/amba-pl011.c: In function 'pl011_set_termios':
drivers/tty/serial/amba-pl011.c:1671:9: error: 'struct uart_amba_port' has no member named 'dmarx'
drivers/tty/serial/amba-pl011.c:1672:6: error: 'struct uart_amba_port' has no member named 'dmarx'
Caused by commit cb06ff102e2d ("ARM: PL011: Add support for Rx DMA buffer
polling"). This build does not have CONFIG_DMA_ENGINE set.
I have reverted that commit for today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2013-04-02 7:57 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 7:57 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-10-28 14:33 linux-next: build failure after merge of the final tree (tty tree related) Stephen Rothwell
2013-10-28 14:49 ` Michal Simek
2013-10-28 16:05 ` Sören Brinkmann
2013-10-28 16:33 ` Greg KH
2013-10-29 7:04 ` Stephen Rothwell
2013-09-27 8:21 Stephen Rothwell
2013-09-28 1:04 ` Greg KH
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 14:08 ` Greg KH
2011-08-25 14:28 ` Timur Tabi
2011-08-25 15:22 ` Timur Tabi
2011-08-25 15:51 ` Stephen Rothwell
2011-08-25 16:09 ` Arnaud Lacombe
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=20130402185747.c4d8c60880025b242953da63@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=chanho.min@lge.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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).