From: Tom Rini <trini@kernel.crashing.org>
To: Tony Mantler <nicoya@apia.dhs.org>
Cc: Linux/m68k <linux-m68k@lists.linux-m68k.org>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: [PATCH] drivers/macintosh/Config.in
Date: Sun, 7 Jan 2001 17:38:05 -0700 [thread overview]
Message-ID: <20010107173805.B19404@opus.bloom.county> (raw)
In-Reply-To: <v04003a08b67ddaff44fe@[24.70.162.12]>; from nicoya@apia.dhs.org on Sun, Jan 07, 2001 at 02:57:30AM -0600
On Sun, Jan 07, 2001 at 02:57:30AM -0600, Tony Mantler wrote:
> At 6:17 PM -0600 1/6/2001, Tom Rini wrote:
> >Hey all. I was wondering what both camps would think of a
> >drivers/macintosh/Config.in? It would simply a few things and remove some
> >duplicated bits. I've attached my first attempt at it, and everything should
> >look the same as before (I did rename some of the ADB driver comments from
> >the m68k side so they matched the others).
> >
> >Comments? (We probably wouldn't see this until 2.5 anyways tho..)
>
> Does the input layer work on the 68k drivers? I don't know that I've ever
> heard of anyone testing it.
Well, it should. It was in the menu :)
> The patch looks fairly sane to me. If it breaks something, it's not very
> hard to fix a config file.
Right. I just wanna make sure everyone like the way it looks. I also (may)
move things like MOL into that file.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-01-08 0:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-07 0:17 [PATCH] drivers/macintosh/Config.in Tom Rini
2001-01-07 8:57 ` Tony Mantler
2001-01-08 0:38 ` Tom Rini [this message]
2001-01-08 1:35 ` Tony Mantler
2001-01-08 9:56 ` Michel Dänzer
2001-01-08 14:55 ` Tom Rini
2001-01-08 2:40 ` Ray Knight
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=20010107173805.B19404@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=nicoya@apia.dhs.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;
as well as URLs for NNTP newsgroup(s).