mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Adrian Bunk <bunk@fs.tum.de>, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: Linux 2.4.20-pre6
Date: Tue, 10 Sep 2002 16:14:24 -0700	[thread overview]
Message-ID: <20020910231424.GA30612@bougret.hpl.hp.com> (raw)

Adrian Bunk wrote :
> >...
> > Alan Cox <alan@lxorguk.ukuu.org.uk>:
> >...
> >   o more irda __FUNCTION__ stuff
> >...
> 
> This adds the use of TIOCM_MODEM_BITS to irtty.c but not the corresponding
> addition of it to asm-i386/termios.h:

	I would personally would have veto'ed that change, because it
will work only on i386 (and PA-Risc), whereas the IrDA stack is
routinely used on ARM and PPC and also work on Alpha.
	That's the kind of shortsighted quick hack that make life
painfull for everybody, because we now have to fix a dozen
platforms. Last time I heard, 2.4.X was supposed to be the "stable"
kernel.
	I would personally perfer the header to define a "default"
value, and only the broken architecture would need to override it
(#undef + #define).
	Actually, the previous solution of having the cruft hidden in
the irtty driver with #ifdef and not poluting the generic kernel was
also pretty good IMHO, and I don't understand why the original author
didn't go along those lines (sure he didn't told me why).

	Of course, I'm opiniated...

	So, as people like quick'n'dirty hacks, just make sure that
TIOCM_MODEM_BITS is also defined in ARM, SH, PPC and Alpha (at least),
just to make sure I'm the only one complaining.

	Thanks in advance...

	Jean

             reply	other threads:[~2002-09-10 23:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-10 23:14 Jean Tourrilhes [this message]
2002-09-11  0:41 ` Alan Cox
2002-09-11  0:40   ` Jean Tourrilhes
  -- strict thread matches above, loose matches on Subject: below --
2002-09-10 21:39 Andreas Kerl
2002-09-10 22:26 ` Alan Cox
2002-09-10 21:12 Tony Spinillo
2002-09-10 20:02 Koos Vriezen
2002-09-10 18:04 Marcelo Tosatti
2002-09-10 22:40 ` Adrian Bunk
2002-09-10 23:01   ` Alan Cox
2002-09-10 23:56 ` Adrian Bunk
2002-09-11 10:55   ` Geert Uytterhoeven
2002-09-11 12:49     ` Joachim Breuer
2002-09-11 19:02       ` Thunder from the hill
2002-09-12 13:27     ` Geert Uytterhoeven
2002-09-11 10:00 ` Oleg Drokin
2002-09-11 10:14   ` Andi Kleen
2002-09-11 10:36     ` Oleg Drokin
2002-09-11 10:51       ` Andi Kleen
2002-09-11 10:59         ` Oleg Drokin

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=20020910231424.GA30612@bougret.hpl.hp.com \
    --to=jt@bougret.hpl.hp.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bunk@fs.tum.de \
    --cc=jt@hpl.hp.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®