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>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: ttydev tree build failure
Date: Wed, 23 Jul 2008 20:55:01 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0807232048440.24017@anakin> (raw)
In-Reply-To: <20080723172837.3d784d85@lxorguk.ukuu.org.uk>
On Wed, 23 Jul 2008, Alan Cox wrote:
> > Update all drivers when making core tty infrastructure changes?
> > Thanks!
>
> I don't have an Amiga with that board, I don't have an obscure VME 68K
> board. The changes required at this point would be tricky to verify
> without hardware, and the upcoming changes will require significant
> changes to all the hardware drivers, which will need someone to actually
> maintain the drivers, or to drop them.
IC, testing/maintaining non-trival changes is a different situation.
But it would still be nice to announce such removals/breakings in advance,
cfr. Documentation/feature-removal-schedule.txt. At least we knew the old
NCR53C9x core was going away, taken with it all drivers depending on it...
Anyone who cares about these drivers (ser_a2232 and vme_scc, perhaps
others?)?
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
next parent reply other threads:[~2008-07-23 18:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080723171743.1436cf2a.sfr@canb.auug.org.au>
[not found] ` <Pine.LNX.4.64.0807231436310.1185@anakin>
[not found] ` <20080723154610.348ffc07@lxorguk.ukuu.org.uk>
[not found] ` <Pine.LNX.4.64.0807231748250.20868@anakin>
[not found] ` <20080723164731.00c163f1@lxorguk.ukuu.org.uk>
[not found] ` <Pine.LNX.4.64.0807231838470.21737@anakin>
[not found] ` <20080723172837.3d784d85@lxorguk.ukuu.org.uk>
2008-07-23 18:55 ` Geert Uytterhoeven [this message]
2009-07-06 3:26 Stephen Rothwell
2009-07-14 4:10 Stephen Rothwell
2009-07-16 5:04 Stephen Rothwell
2009-07-17 3:12 Stephen Rothwell
2009-07-24 5:54 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=Pine.LNX.4.64.0807232048440.24017@anakin \
--to=geert@linux-m68k.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®