From: David Miller <davem@davemloft.net>
To: rbrito@ime.usp.br
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] powerpc: convert mace to netdev_ops
Date: Sun, 03 May 2009 14:15:24 -0700 (PDT) [thread overview]
Message-ID: <20090503.141524.253766195.davem@davemloft.net> (raw)
In-Reply-To: <20090503114820.GA14926@ime.usp.br>
From: Rog=E9rio Brito <rbrito@ime.usp.br>
Date: Sun, 3 May 2009 08:48:20 -0300
> I hope that this version is a slightly better fix to convert mace to
> netdev_ops.
> =
> This is against this morning's net-2.6 tree.
> =
> Signed-off-by: Rog=E9rio Brito <rbrito@ime.usp.br>
I'll apply this, thanks! I made one change however.
> @@ -798,6 +807,13 @@ static irqreturn_t mace_interrupt(int irq, void =
*dev_id)
> return IRQ_HANDLED;
> }
> =
> +/*
> + * In the following, the parameter "data" is treated like a pointer,=
> + * which is probably OK for 32 bit arches, but not for 64.
> + *
> + * (Are mace's found on any newer machines??) -- rbrito
> + *
> + */
> static void mace_tx_timeout(unsigned long data)
> {
> struct net_device *dev =3D (struct net_device *) data;
I left this new comment out, as this is a common idiom (passing opaque
data as an 'unsigned long' argument to a callback) and casting it to a
pointer.
It also works perfectly fine on all 32-bit and 64-bit platforms.
next prev parent reply other threads:[~2009-05-03 21:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-26 15:57 [2.6.30-rc3] powerpc: compilation error of mace module Rogério Brito
2009-04-27 6:06 ` David Miller
2009-04-27 12:16 ` [PATCH] powerpc: convert mace to netdev_ops (was: Re: [2.6.30-rc3] powerpc: compilation error of mace module) Rogério Brito
2009-04-27 12:42 ` [PATCH] powerpc: convert mace to netdev_ops David Miller
2009-04-27 14:20 ` Rogério Brito
2009-05-03 11:48 ` Rogério Brito
2009-05-03 21:15 ` David Miller [this message]
2009-05-03 21:20 ` David Miller
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=20090503.141524.253766195.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=paulus@samba.org \
--cc=rbrito@ime.usp.br \
/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).