From: Dave Jones <davej@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-next@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
LKML <linux-kernel@vger.kernel.org>,
ppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] serial: fix struct uart_info change fallout
Date: Mon, 21 Jul 2008 20:38:14 -0400 [thread overview]
Message-ID: <20080722003814.GA14809@redhat.com> (raw)
In-Reply-To: <20080722102520.ca801ab5.sfr@canb.auug.org.au>
On Tue, Jul 22, 2008 at 10:25:20AM +1000, Stephen Rothwell wrote:
> Hi Linus, Alan,
>
> Today's linux-next (actually just Linus' tree) build (powerpc
> ppc64_defconfig) failed like this:
>
> drivers/serial/serial_txx9.c: In function 'receive_chars':
> drivers/serial/serial_txx9.c:275: error: 'struct uart_info' has no member named 'tty'
> drivers/serial/icom.c: In function 'recv_interrupt':
> drivers/serial/icom.c:733: error: 'struct uart_info' has no member named 'tty'
That's the same pair of patches I sent earlier, which apparently were
"Already in the ttydev tree" which should be in linux-next ?
Dave
--
http://www.codemonkey.org.uk
WARNING: multiple messages have this Message-ID (diff)
From: Dave Jones <davej@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: ppc-dev <linuxppc-dev@ozlabs.org>,
linux-next@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] serial: fix struct uart_info change fallout
Date: Mon, 21 Jul 2008 20:38:14 -0400 [thread overview]
Message-ID: <20080722003814.GA14809@redhat.com> (raw)
In-Reply-To: <20080722102520.ca801ab5.sfr@canb.auug.org.au>
On Tue, Jul 22, 2008 at 10:25:20AM +1000, Stephen Rothwell wrote:
> Hi Linus, Alan,
>
> Today's linux-next (actually just Linus' tree) build (powerpc
> ppc64_defconfig) failed like this:
>
> drivers/serial/serial_txx9.c: In function 'receive_chars':
> drivers/serial/serial_txx9.c:275: error: 'struct uart_info' has no member named 'tty'
> drivers/serial/icom.c: In function 'recv_interrupt':
> drivers/serial/icom.c:733: error: 'struct uart_info' has no member named 'tty'
That's the same pair of patches I sent earlier, which apparently were
"Already in the ttydev tree" which should be in linux-next ?
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2008-07-22 0:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 0:25 [PATCH] serial: fix struct uart_info change fallout Stephen Rothwell
2008-07-22 0:25 ` Stephen Rothwell
2008-07-22 0:38 ` Dave Jones [this message]
2008-07-22 0:38 ` Dave Jones
2008-07-22 1:34 ` Stephen Rothwell
2008-07-22 1:34 ` Stephen Rothwell
2008-07-22 2:00 ` Alan Cox
2008-07-22 2:00 ` Alan Cox
2008-07-22 1:58 ` Alan Cox
2008-07-22 1:58 ` Alan Cox
2008-07-22 3:01 ` Stephen Rothwell
2008-07-22 3:01 ` Stephen Rothwell
2008-07-22 10:44 ` Alan Cox
2008-07-22 10:44 ` Alan Cox
2008-07-22 15:49 ` Stephen Rothwell
2008-07-22 15:49 ` Stephen Rothwell
2008-07-22 15:59 ` Alan Cox
2008-07-22 15:59 ` Alan Cox
2008-07-22 16:22 ` Stephen Rothwell
2008-07-22 16:22 ` 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=20080722003814.GA14809@redhat.com \
--to=davej@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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 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.