linux-kernel - Re: [PATCH] serial: fix struct uart

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080722030011.6b0d8137@lxorguk.ukuu.org.uk>
Date:	Tue, 22 Jul 2008 03:00:11 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Dave Jones <davej@...hat.com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	ppc-dev <linuxppc-dev@...abs.org>
Subject: Re: [PATCH] serial: fix struct uart_info change fallout

On Mon, 21 Jul 2008 20:38:14 -0400
Dave Jones <davej@...hat.com> wrote:

> 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 ?

And are in Linux next, and would be in the Linus submission queue except
that everyone keeps patching tty files from other trees.

<mutter>

Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/