From: "Matthew D. Pitts" <mpitts@suite224.net>
To: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH: NEW SUBARCHITECTURE FOR 2.5.21] support for NCR voyager (3/4/5xxx series)
Date: Thu, 13 Jun 2002 22:19:49 -0400 [thread overview]
Message-ID: <001e01c21349$f5f66060$f7f583d0@pcs686> (raw)
In-Reply-To: <davej@suse.de> <200206140013.g5E0DQR25561@localhost.localdomain> <20020614024547.H16772@suse.de>
> > > Sounds quite logical. What does the current patches you have do ?
I've
> > > not had chance to look at them yet.
> > It creates directories `generic' for the standard pc and `visws'. The
voyager
> > patch creates a `voyager' directory. Alternatively, these could be
`mach-pc',
> > `mach-visws' and `mach-voyager'.
>
> Yeah, I think mach-foo would be more aesthetically pleasing, so I'll
> cast my vote for that one. If nothing else, it makes it obvious that
> the subdir isn't important if you don't care about $subarch
>
I think it would be a good idea as well.
Matthew
next prev parent reply other threads:[~2002-06-14 2:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-09 17:54 [PATCH: NEW SUBARCHITECTURE FOR 2.5.21] support for NCR voyager (3/4/5xxx series) James Bottomley
2002-06-13 8:20 ` Andrey Panin
2002-06-13 15:48 ` James Bottomley
2002-06-13 23:17 ` Dave Jones
2002-06-14 0:13 ` James Bottomley
2002-06-14 0:45 ` Dave Jones
2002-06-14 2:19 ` Matthew D. Pitts [this message]
2002-06-14 2:52 ` SCSI host/channel/lun/part to /dev/sd* or maj/minor mapping Mark Atwood
2002-06-14 13:41 ` [PATCH: NEW SUBARCHITECTURE FOR 2.5.21] support for NCR voyager (3/4/5xxx series) Andrey Panin
2002-06-14 13:49 ` Dave Jones
2002-06-14 13:52 ` Andrey Panin
2002-06-14 14:14 ` James Bottomley
2002-06-14 14:16 ` Dave Jones
2002-06-17 13:36 ` Andrey Panin
2002-06-17 14:03 ` Dave Jones
2002-06-16 0:00 ` James Bottomley
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='001e01c21349$f5f66060$f7f583d0@pcs686' \
--to=mpitts@suite224.net \
--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