From: Pete Zaitcev <zaitcev@redhat.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Altix console driver
Date: Wed, 17 Sep 2003 19:45:23 -0400 [thread overview]
Message-ID: <200309172345.h8HNjNs13415@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.1063838640.11239.linux-kernel2news@redhat.com>
>> Just a simple addition to drivers/char for the Altix serial console.
>>
>> MAINTAINERS | 6
>> drivers/char/Kconfig | 16
>> drivers/char/Makefile | 1
>> drivers/char/sn_serial.c | 1189 +++++++++++++++++++++++++++++++++++++++++++++++
>
> Would it be more appropriate to place this under arch/ia64?
It was discussed on other occasions, and it "was decided"
(sprinkled with holy penguin pee) that such things go into
drivers/, e.g. drivers/serial/sunsu.c is Sun-specific,
but it helps to keep it near drivers/serial/8250.c, for
diffing. If an additional API is involved, e.g.
sbus_alloc_consistent, drivers get a subdir like
drivers/sbus or drivers/s390. Also, you never know
when sharing hits you across the head, e.g. sparc, sparc64,
and m68k (for sun3) share some drivers.
-- Pete
next prev parent reply other threads:[~2003-09-17 23:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-17 22:24 [PATCH] Altix console driver Jesse Barnes
2003-09-17 22:21 ` Andrew Morton
2003-09-17 22:55 ` Jesse Barnes
2003-09-18 7:05 ` Christoph Hellwig
2003-09-18 12:09 ` Alan Cox
2003-09-19 15:21 ` Jesse Barnes
2003-09-19 15:33 ` Alan Cox
2003-09-20 19:24 ` Jamie Lokier
2003-09-20 22:44 ` Alan Cox
[not found] ` <mailman.1063838640.11239.linux-kernel2news@redhat.com>
2003-09-17 23:45 ` Pete Zaitcev [this message]
2003-09-18 7:27 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2003-10-21 21:26 Patrick Gefre
2003-10-21 22:00 ` Andrew Morton
2003-10-21 22:47 ` Pat Gefre
2003-10-22 14:07 ` Christoph Hellwig
2003-10-22 14:39 ` Pat Gefre
2003-10-22 14:51 ` Christoph Hellwig
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=200309172345.h8HNjNs13415@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=akpm@osdl.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.