linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Matt Porter <porter@cox.net>
To: Eugene Surovegin <ebs@innocent.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: [PATCH] correct initialization sequence in ppc405_enet_open
Date: Thu, 21 Nov 2002 08:47:33 -0700	[thread overview]
Message-ID: <20021121084733.B8252@home.com> (raw)
In-Reply-To: <5.1.0.14.2.20021120212220.00aebfa0@pop.prodigy.net>; from ebs@innocent.com on Wed, Nov 20, 2002 at 09:47:34PM -0800


On Wed, Nov 20, 2002 at 09:47:34PM -0800, Eugene Surovegin wrote:
>
> Hi!
>
> This patch fixes problem in drivers/net/ibm_ocp/ibm_ocp_enet.c.

<snip>

> This patch is against current devel_2_4, but I think should apply without
> any problems to devel_2_5 also.

Looks good, applied to both trees.

Thanks,
--
Matt Porter
porter@cox.net
This is Linux Country. On a quiet night, you can hear Windows reboot.

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

      reply	other threads:[~2002-11-21 15:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-21  5:47 [PATCH] correct initialization sequence in ppc405_enet_open Eugene Surovegin
2002-11-21 15:47 ` Matt Porter [this message]

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=20021121084733.B8252@home.com \
    --to=porter@cox.net \
    --cc=ebs@innocent.com \
    --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).