From: Armin Kuster <akuster@mvista.com>
To: andrew may <acmay@acmay.homeip.net>
Cc: linuxppc-embedded@lists.linuxppc.org, Dan Malek <dan@mvista.com>
Subject: Re: [PATCH] some fixups for ppc405_enet init code
Date: Mon, 10 Sep 2001 10:53:03 -0700 [thread overview]
Message-ID: <3B9CFDFF.2A3D02AE@mvista.com> (raw)
In-Reply-To: 20010907201341.A1856@ecam.san.rr.com
andrew may wrote:
>
> This change is for Config.in and the Makefile to add the
> ppc405_enet driver.
>
> I also removed the _probe1 function and moved the code down
> into the init function. This was done for 2 reasons: 1 the
> dev->name is not know until the device is registered and
> 2 so the code would be removed after init.
>
> I also added a kfree of the private data when the register
> fails and when the module is removed.
>
> ------------------------------------------------------------------------
>
> ppc_enet.diffName: ppc_enet.diff
> Type: Plain Text (text/plain)
Thanks, I'll make the appropriate changes.
-- armin
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-09-10 17:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-08 3:13 [PATCH] some fixups for ppc405_enet init code andrew may
2001-09-10 17:53 ` Armin Kuster [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=3B9CFDFF.2A3D02AE@mvista.com \
--to=akuster@mvista.com \
--cc=acmay@acmay.homeip.net \
--cc=dan@mvista.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).