netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: clsoto@linux.vnet.ibm.com
To: netdev@vger.kernel.org
Cc: clsoto@linux.vnet.ibm.com, brking@linux.vnet.ibm.com
Subject: [PATCH 0/1] mlx4: mlx4_core failed to load
Date: Mon, 28 Apr 2014 13:33:30 -0500	[thread overview]
Message-ID: <20140428183330.201681971@linux.vnet.ibm.com> (raw)

This is for a case where mlx4_core fails to load.

 drivers/net/ethernet/mellanox/mlx4/main.c |    7 -------
 include/linux/mlx4/device.h               |    1 -
 2 files changed, 8 deletions(-)

Carol

-- 

             reply	other threads:[~2014-04-28 19:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-28 18:33 clsoto [this message]
2014-04-28 18:33 ` [PATCH 1/1] mlx4: mlx4_core failed to load if use_prio argument is used clsoto
2014-04-28 19:59 ` [PATCH 0/1] mlx4: mlx4_core failed to load David Miller
2014-05-13 15:06   ` Carol Soto
2014-05-13 16:32     ` David Miller
2014-05-13 18:14       ` Carol Soto

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=20140428183330.201681971@linux.vnet.ibm.com \
    --to=clsoto@linux.vnet.ibm.com \
    --cc=brking@linux.vnet.ibm.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).