linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: benh@kernel.crashing.org
To: <paulus@samba.org>, Troy Benjegerdes <hozer@drgw.net>
Cc: <linux-galileo@source.mvista.com>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: GT64260 merge warning
Date: Tue, 2 Apr 2002 23:15:44 +0100	[thread overview]
Message-ID: <20020402221544.21559@mailhost.mipsys.com> (raw)
In-Reply-To: <15530.40918.517084.226235@argo.ozlabs.ibm.com>


>> I'm getting close to a point where I want to start merging appropriate
>> things from the linuxppc_2_4_galileo tree on source.mvista.com into
>> 2_4_devel.
>
>I'll be interested to see it - I'm in code review mode at the moment. :)
>
>> The first thing I'm going to do is a moderately large cleanup to
>> drivers/net/gt64260_eth.c.
>
>Good.  Can you get rid of the config option for the MAC address?
>Please? :)  I suggest that we define a BI_MAC_ADDRESS bi_rec type
>which is used to pass in a default MAC address for the system, and we
>use that (single) MAC address for all the ethernet interfaces on the
>system which don't have any way to find out a MAC address for that
>specific interface.

I'm almost done with the new bi_rec stuffs, I'll push it to _2_5
this week as soon as I've tested a bit.

Ben.


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

  reply	other threads:[~2002-04-02 22:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-03  5:04 GT64260 merge warning Troy Benjegerdes
2002-04-03  6:23 ` Paul Mackerras
2002-04-02 22:15   ` benh [this message]
2002-04-03 22:11     ` Paul Mackerras
2002-04-03  8:53       ` benh
2002-04-03 19:24   ` Troy Benjegerdes
2002-04-03  6:47     ` Benjamin Herrenschmidt
2002-04-03 22:02     ` Paul Mackerras
2002-04-04  2:26       ` Dan Malek
2002-04-04  7:51         ` Geert Uytterhoeven
2002-04-04 17:06           ` [Linux-galileo] " Nye Liu

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=20020402221544.21559@mailhost.mipsys.com \
    --to=benh@kernel.crashing.org \
    --cc=hozer@drgw.net \
    --cc=linux-galileo@source.mvista.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=paulus@samba.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).