Linux-Next discussions
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-next@vger.kernel.org
Subject: linux-next: ttydev tree build failure
Date: Wed, 20 Aug 2008 18:23:53 +1000	[thread overview]
Message-ID: <20080820182353.024d5a9e.sfr@canb.auug.org.au> (raw)

Hi Alan,

Today's linux-next build (powerpc allnoconfig) failed like this:

drivers/char/pty.c:420: error: 'pty_bsd_ioctl' undeclared here (not in a function)

Caused by 5265223407c8eed1b023aca77492c631e2676f5c ("tty-fix-shutdown").
I applied the following patch (which may not be correct).

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Wed, 20 Aug 2008 18:21:53 +1000
Subject: [PATCH] ttydev: fix for tty-fix-shutdown

Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
 drivers/char/pty.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/drivers/char/pty.c b/drivers/char/pty.c
index fbd215b..2cae85c 100644
--- a/drivers/char/pty.c
+++ b/drivers/char/pty.c
@@ -417,7 +417,7 @@ static const struct tty_operations pts_unix98_ops = {
 	.chars_in_buffer = pty_chars_in_buffer,
 	.unthrottle = pty_unthrottle,
 	.set_termios = pty_set_termios,
-	.ioctl = pty_bsd_ioctl,
+	.ioctl = pty_unix98_ioctl,
 	.shutdown = pty_shutdown
 };
 
-- 
1.5.6.3

             reply	other threads:[~2008-08-20  8:23 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-20  8:23 Stephen Rothwell [this message]
2008-08-20  8:26 ` linux-next: ttydev tree build failure Alan Cox
2008-08-20  9:08   ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2009-07-24  5:54 Stephen Rothwell
2009-07-17  3:12 Stephen Rothwell
2009-07-16  5:04 Stephen Rothwell
2009-07-14  4:10 Stephen Rothwell
2009-07-06  3:26 Stephen Rothwell
2009-04-20  3:09 Stephen Rothwell
2008-11-24  5:13 Stephen Rothwell
2008-11-24  9:59 ` Alan Cox
2008-10-23  6:29 Stephen Rothwell
2008-10-23  7:34 ` Alan Cox
2008-10-23  7:35   ` Benjamin Herrenschmidt
2008-10-24  4:58   ` Stephen Rothwell
2008-10-23 10:28 ` Hendrik Brueckner
2008-10-20  8:06 Stephen Rothwell
2008-10-20 21:48 ` Lee Howard
2008-10-21  9:33   ` Alan Cox
2008-10-15  9:39 Stephen Rothwell
2008-09-02  7:23 Stephen Rothwell
2008-09-02  9:22 ` Alan Cox
2008-07-23  7:17 Stephen Rothwell
2008-07-23 12:39 ` Geert Uytterhoeven
2008-07-23 14:46   ` Alan Cox
2008-07-23 15:49     ` Geert Uytterhoeven
2008-07-23 15:47       ` Alan Cox
2008-07-23 16:39         ` Geert Uytterhoeven
2008-07-23 16:28           ` Alan Cox
2008-07-23 18:55             ` Geert Uytterhoeven
2008-07-18 21:34 Aleksey Gorelov
2008-07-18  8:59 Stephen Rothwell
2008-07-02  5:30 Stephen Rothwell
2008-07-02 18:10 ` Randy Dunlap
2008-07-02 19:54   ` Alan Cox
2008-07-02  5:19 Stephen Rothwell
2008-07-02  5:21 ` Stephen Rothwell
2008-07-02  8:09 ` Alan Cox
2008-07-02  5:08 Stephen Rothwell
2008-07-02  8:05 ` Alan Cox
2008-07-01 14:17 Stephen Rothwell
2008-07-01 14:23 ` Alan Cox
2008-07-01 14:51   ` Stephen Rothwell
2008-07-01 15:27     ` Greg KH
2008-07-01 15:36     ` 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=20080820182353.024d5a9e.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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