From: andrew may <acmay@acmay.homeip.net>
To: Armin <akuster@pacbell.net>
Cc: andrew may <acmay@acmay.homeip.net>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: [PATCH] another for ibm_ocp_enet gzip'd
Date: Mon, 18 Mar 2002 14:56:04 -0800 [thread overview]
Message-ID: <20020318145604.B6687@ecam.san.rr.com> (raw)
In-Reply-To: <3C95FF7C.7050300@pacbell.net>
On Mon, Mar 18, 2002 at 02:53:48PM +0000, Armin wrote:
> andrew may wrote:
>
> > +#Do we want CONFIG_IBM_OCP_MAL_CNT ?
>
> No
Well then you get to update the makefile when
we start having more MALs around.
> > +ibm_ocp_mal.c: mal.sh
> > + $(SH) ./mal.sh 2 >ibm_ocp_mal.c
> > +
> >
>
>
> And this get applied on top of your first patch?
Yes, how else would get mal.sh. There was the first
patch, and a second patch that fixed up mal.sh.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-03-18 22:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 19:41 [PATCH] another for ibm_ocp_enet gzip'd andrew may
2002-03-15 20:05 ` Tom Rini
2002-03-15 22:25 ` andrew may
2002-03-15 22:31 ` Tom Rini
2002-03-18 22:25 ` andrew may
2002-03-18 14:53 ` Armin
2002-03-18 22:56 ` andrew may [this message]
2002-03-19 0:28 ` Tom Rini
2002-03-19 0:54 ` andrew may
2002-03-19 1:01 ` Tom Rini
2002-03-15 20:06 ` Tom Rini
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=20020318145604.B6687@ecam.san.rr.com \
--to=acmay@acmay.homeip.net \
--cc=akuster@pacbell.net \
--cc=linuxppc-embedded@lists.linuxppc.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).