From: "Eilon Greenstein" <eilong@broadcom.com>
To: "Harvey Harrison" <harvey.harrison@gmail.com>
Cc: "David Miller" <davem@davemloft.net>,
linux-netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] bnx2: annotate bp->phy_lock functions
Date: Tue, 20 Jan 2009 15:27:42 +0200 [thread overview]
Message-ID: <1232458062.29087.5.camel@lb-tlvb-eliezer> (raw)
In-Reply-To: <1232396961.13386.7.camel@brick>
On Mon, 2009-01-19 at 12:29 -0800, Harvey Harrison wrote:
[...]
> Whoops, bnx2 != bnx2x....that driver needs serious help in the endianess
> department, but it doesn't actually lok to hard to sort out as it seems
> most of the warnings come about as the hardware structs are just not
> annotated, but the correct accessors seem to be in place in the code.
>
> In addition, there are piles of macros in the driver that really shouldn't
> be. I'll have a look this afternoon at some of the low-hanging fruit.
>
> Harvey
Thanks Harvey, I appreciate the help
Eilon
next prev parent reply other threads:[~2009-01-20 13:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-19 20:11 [PATCH] bnx2: annotate bp->phy_lock functions Harvey Harrison
2009-01-19 20:29 ` Harvey Harrison
2009-01-20 13:27 ` Eilon Greenstein [this message]
2009-01-20 1:27 ` 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=1232458062.29087.5.camel@lb-tlvb-eliezer \
--to=eilong@broadcom.com \
--cc=davem@davemloft.net \
--cc=harvey.harrison@gmail.com \
--cc=netdev@vger.kernel.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