From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Roman Zippel <zippel@linux-m68k.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
akpm@osdl.org, rmk@arm.linux.kernel.org, spyro@f2s.com,
starvik@axis.com, ysato@users.sourceforge.jp, "Luck,
Tony" <tony.luck@intel.com>,
takata@linux-m32r.org, chris@zankel.net,
uclinux-v850@lsi.nec.co.jp, kyle@parisc-linux.org,
linux-mips@linux-mips.org
Subject: Re: [PATCH] m68k: Enable arbitary speed tty support
Date: Wed, 23 May 2007 22:38:21 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0705232233360.10610@anakin> (raw)
In-Reply-To: <20070523205645.07b03581@the-village.bc.nu>
On Wed, 23 May 2007, Alan Cox wrote:
> > > +#define TCSETS2 _IOW('T',0x2B, struct termios2)
> > > +#define TCSETSW2 _IOW('T',0x2C, struct termios2)
> > > +#define TCSETSF2 _IOW('T',0x2D, struct termios2)
> >
> > Where is `struct termios2' defined? Right now it doesn't compile because
> > of that.
> >
>
> Sorry, shortage of qualified gnomes: One of them forgot to post this diff first
>
> Add the termios2 structure ready for enabling on most platforms. One or two like
> Sparc are plain weird so have been left alone. Most can use the same structure as
> ktermios for termios2 (ie the newer ioctl uses the structure matching the current
> kernel structure)
Why not `#define termios2 ktermios' (or vice versa) on platforms where
they are the same?
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 prev parent reply other threads:[~2007-05-23 20:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070523174446.37abfa7a@the-village.bc.nu>
2007-05-23 19:18 ` Geert Uytterhoeven
2007-05-23 19:56 ` Alan Cox
2007-05-23 20:38 ` Geert Uytterhoeven [this message]
2007-05-23 21:30 ` Alan Cox
2007-05-23 22:40 ` Andreas Schwab
2007-05-24 20:40 ` Andrew Morton
2007-05-25 0:00 ` 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.0705232233360.10610@anakin \
--to=geert@linux-m68k.org \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=chris@zankel.net \
--cc=kyle@parisc-linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=rmk@arm.linux.kernel.org \
--cc=spyro@f2s.com \
--cc=starvik@axis.com \
--cc=takata@linux-m32r.org \
--cc=tony.luck@intel.com \
--cc=uclinux-v850@lsi.nec.co.jp \
--cc=ysato@users.sourceforge.jp \
--cc=zippel@linux-m68k.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®