From: Andrew Morton <akpm@linux-foundation.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Roman Zippel <zippel@linux-m68k.org>,
Linux Kernel Development <linux-kernel@vger.kernel.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: Thu, 24 May 2007 13:40:15 -0700 [thread overview]
Message-ID: <20070524134015.e89843db.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070523205645.07b03581@the-village.bc.nu>
Alan, I'm all dazed and confused about these patches:
arm-enable-arbitary-speed-tty-ioctls-and-split.patch
arm26-enable-arbitary-speed-tty-ioctls-and-split.patch
ia64-arbitary-speed-tty-ioctl-support.patch
xtensa-enable-arbitary-tty-speed-setting-ioctls.patch
h8300-enable-arbitary-speed-tty-port-setup.patch
m32r-enable-arbitary-speed-tty-rate-setting.patch
etrax-enable-arbitary-speed-setting-on-tty-ports.patch
v850-enable-arbitary-speed-tty-ioctls.patch
lots-of-architectures-enable-arbitary-speed-tty-support.patch
are there any interdependencies here, or can the various patches
go into the various trees in random order without ill effects?
Thanks.
next prev parent reply other threads:[~2007-05-24 20:42 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 ` [PATCH] m68k: Enable arbitary speed tty support Geert Uytterhoeven
2007-05-23 19:56 ` Alan Cox
2007-05-23 20:38 ` Geert Uytterhoeven
2007-05-23 21:30 ` Alan Cox
2007-05-23 22:40 ` Andreas Schwab
2007-05-24 20:40 ` Andrew Morton [this message]
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=20070524134015.e89843db.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=chris@zankel.net \
--cc=geert@linux-m68k.org \
--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