linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org,
	Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: linux-next: ttydev tree build failure
Date: Wed, 23 Jul 2008 18:39:37 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0807231838470.21737@anakin> (raw)
In-Reply-To: <20080723164731.00c163f1@lxorguk.ukuu.org.uk>

	Hi Alan,

On Wed, 23 Jul 2008, Alan Cox wrote:
> On Wed, 23 Jul 2008 17:49:13 +0200 (CEST)
> Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > On Wed, 23 Jul 2008, Alan Cox wrote:
> > > On Wed, 23 Jul 2008 14:39:08 +0200 (CEST)
> > > Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > > > On Wed, 23 Jul 2008, Stephen Rothwell wrote:
> > > > > Today's linux-next build (m68k defconfig) failed like this:
> > > > > 
> > > > > drivers/char/vme_scc.c:186: error: 'struct gs_port' has no member named 'open_wait'
> > > > 
> > > > Not just in linux-next, also in mainline, while these problems have been
> > > > reported before.
> > > 
> > > And at the time I asked if anyone was using this hardware and if so would
> > > they send patches. Shall I send Linus patches to delete them or is anyone
> > > actually using this stuff ?
> > 
> > Sorry, I did not see that question.
> 
> No problem - what do you want me to do however ?

Update all drivers when making core tty infrastructure changes?
Thanks!

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

  reply	other threads:[~2008-07-23 16:39 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-23  7:17 linux-next: ttydev tree build failure 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 [this message]
2008-07-23 16:28           ` Alan Cox
2008-07-23 18:55             ` Geert Uytterhoeven
  -- 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-08-20  8:23 Stephen Rothwell
2008-08-20  8:26 ` Alan Cox
2008-08-20  9:08   ` Stephen Rothwell
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=Pine.LNX.4.64.0807231838470.21737@anakin \
    --to=geert@linux-m68k.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-m68k@vger.kernel.org \
    --cc=linux-next@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).