From: Ben Hutchings <bhutchings@solarflare.com>
To: Eilon Greenstein <eilong@broadcom.com>
Cc: David Miller <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH 03/41]bnx2x: MSI support
Date: Thu, 12 Feb 2009 20:47:48 +0000 [thread overview]
Message-ID: <1234471668.3583.26.camel@achroite> (raw)
In-Reply-To: <1234471059.4798.7.camel@lb-tlvb-eliezer>
On Thu, 2009-02-12 at 22:37 +0200, Eilon Greenstein wrote:
> On Thu, 2009-02-12 at 10:52 -0800, Ben Hutchings wrote:
> Hi Ben!
>
> It's always a pleasure to see how fast you respond. I really appreciate
> the fact that you take the time to review my patches. Thanks!
>
> > On Thu, 2009-02-12 at 20:36 +0200, Eilon Greenstein wrote:
> > [...]
> > > @@ -5359,9 +5360,28 @@
> > > #define PCICFG_PM_CSR_STATE (0x3<<0)
> > > #define PCICFG_PM_CSR_PME_ENABLE (1<<8)
> > > #define PCICFG_PM_CSR_PME_STATUS (1<<15)
> > > +#define PCICFG_MSI_CAP_ID 0x58
> >
> > This appears to be a capability offset, not a capability id! You might
> > also consider not hard-coding it.
>
> You are right - those are the offset for this device. I find it easier to
> debug when I have the offsets at hand without the need to parse the
> capabilities linked list. Since the offsets will not change for this
> generation of chips, I don't see the harm in providing the explicit
> offsets. I assume that the driver will require major changes for a new
> generation even if I will use the capabilities ID...
I agree, the run-time lookup is not really necessary. But please fix
the name.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2009-02-12 20:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 18:36 [PATCH 03/41]bnx2x: MSI support Eilon Greenstein
2009-02-12 18:52 ` Ben Hutchings
2009-02-12 20:37 ` Eilon Greenstein
2009-02-12 20:47 ` Ben Hutchings [this message]
2009-02-12 20:55 ` Eilon Greenstein
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=1234471668.3583.26.camel@achroite \
--to=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=eilong@broadcom.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;
as well as URLs for NNTP newsgroup(s).