From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org
Subject: Re: linux-next: Tree for Jan 23 (pch_uart.c)
Date: Wed, 23 Jan 2013 15:28:38 -0800 [thread overview]
Message-ID: <51007226.1040604@infradead.org> (raw)
In-Reply-To: <20130123174336.47c0113740a14da7f6a92187@canb.auug.org.au>
On 01/22/13 22:43, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130122:
>
on i386:
CC [M] drivers/tty/serial/pch_uart.o
drivers/tty/serial/pch_uart.c: In function 'pch_uart_hal_read':
drivers/tty/serial/pch_uart.c:572:11: error: 'struct uart_port' has no member named 'sysrq'
make[4]: *** [drivers/tty/serial/pch_uart.o] Error 1
when SERIAL_PCH_UART_CONSOLE is not enabled.
--
~Randy
next parent reply other threads:[~2013-01-23 23:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130123174336.47c0113740a14da7f6a92187@canb.auug.org.au>
2013-01-23 23:28 ` Randy Dunlap [this message]
2013-01-24 2:06 ` linux-next: Tree for Jan 23 (pch_uart.c) Stephen Rothwell
2013-01-24 2:30 ` Liang Li
2013-01-24 4:15 ` Stephen Rothwell
2013-01-24 4:25 ` Liang Li
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=51007226.1040604@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-serial@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 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).