linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Tony Mantler <nicoya@apia.dhs.org>
To: Tom Rini <trini@kernel.crashing.org>,
	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 02:57:30 -0600	[thread overview]
Message-ID: <v04003a08b67ddaff44fe@[24.70.162.12]> (raw)
In-Reply-To: <20010106171733.M556@opus.bloom.county>


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.

The patch looks fairly sane to me. If it breaks something, it's not very
hard to fix a config file.


Cheers - Tony 'Nicoya' Mantler :)


--
Tony "Nicoya" Mantler - Renaissance Nerd Extraordinaire - nicoya@apia.dhs.org
Winnipeg, Manitoba, Canada           --           http://nicoya.feline.pp.se/

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-01-07  8:57 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 [this message]
2001-01-08  0:38   ` Tom Rini
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='v04003a08b67ddaff44fe@[24.70.162.12]' \
    --to=nicoya@apia.dhs.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=trini@kernel.crashing.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).