From: David Miller <davem@davemloft.net>
To: yevgenyp@mellanox.co.il
Cc: netdev@vger.kernel.org, jackm@dev.mellanox.co.il
Subject: Re: [PATCH net] mlx4_core: Do not map BF area if capability is 0
Date: Mon, 20 Feb 2012 19:26:54 -0500 (EST) [thread overview]
Message-ID: <20120220.192654.417785054157102848.davem@davemloft.net> (raw)
In-Reply-To: <4F41F88C.3070607@mellanox.co.il>
From: Yevgeny Petrilin <yevgenyp@mellanox.co.il>
Date: Mon, 20 Feb 2012 09:38:52 +0200
> From: Jack Morgenstein <jackm@dev.mellanox.co.il>
>
> BF can be disabled in some cases, the capability field, bf_reg_size is set
> to zero in this case. Don't map the BF area in this case, it would cause
> failures. In addition, leaving the BF area unmapped
> also alerts the ETH driver to not use BF.
>
> Signed-off-by: Jack Morgenstein <jackm@dev.mellanox.co.il>
Applied, thanks.
prev parent reply other threads:[~2012-02-21 0:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 7:38 [PATCH net] mlx4_core: Do not map BF area if capability is 0 Yevgeny Petrilin
2012-02-21 0:26 ` David Miller [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=20120220.192654.417785054157102848.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jackm@dev.mellanox.co.il \
--cc=netdev@vger.kernel.org \
--cc=yevgenyp@mellanox.co.il \
/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).