From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Sean MacLennan <smaclennan@pikatech.com>
Cc: linuxppc-dev@ozlabs.org, Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH] emac/zmii link warnings
Date: Thu, 14 Feb 2008 09:30:14 -0600 [thread overview]
Message-ID: <20080214093014.14e71d4e@zod.rchland.ibm.com> (raw)
In-Reply-To: <47AA9251.5020007@pikatech.com>
On Thu, 07 Feb 2008 00:08:33 -0500
Sean MacLennan <smaclennan@pikatech.com> wrote:
> Ok, here is my best shot at removing the warnings. It seems to me that
> functions called from a dev_init section should not be dev_exit.
This seems to fix those specific warnings, but there are others lurking
in some of the other files (rgmii, tah, etc). We should probably get
those fixed up too.
josh
prev parent reply other threads:[~2008-02-14 15:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 4:15 emac/zmii link warnings Sean MacLennan
2008-01-15 4:27 ` Stephen Rothwell
2008-01-15 4:45 ` Sean MacLennan
2008-01-15 5:26 ` Stephen Rothwell
2008-01-15 5:45 ` Sean MacLennan
2008-02-07 5:08 ` [PATCH] " Sean MacLennan
2008-02-14 15:30 ` Josh Boyer [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=20080214093014.14e71d4e@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=sfr@canb.auug.org.au \
--cc=smaclennan@pikatech.com \
/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).