linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wei Yang <weiyang@linux.vnet.ibm.com>
To: Or Gerlitz <ogerlitz@mellanox.com>
Cc: Wei Yang <weiyang@linux.vnet.ibm.com>,
	linux-pci@vger.kernel.org, yinghai@kernel.org,
	bhelgaas@google.com, amirv@mellanox.com,
	jackm@dev.mellanox.co.il, eugenia@mellanox.com,
	Guo Chao <yan@linux.vnet.ibm.com>,
	Gavin Shan <shangw@linux.vnet.ibm.com>,
	Benjamin Herrenschmidt <benh@au1.ibm.com>
Subject: Re: mlx4_core probe error after applying Yinghai's patch
Date: Tue, 14 Jan 2014 16:52:44 +0800	[thread overview]
Message-ID: <20140114085244.GA27684@richard> (raw)
In-Reply-To: <52D4F7C8.50706@mellanox.com>

On Tue, Jan 14, 2014 at 10:39:36AM +0200, Or Gerlitz wrote:
>On 14/01/2014 10:27, Wei Yang wrote:
>>You can find the first three patches here:
>>https://git.kernel.org/cgit/linux/kernel/git/helgaas/pci.git/  pci/resource
>>
>>And the last one is here:
>>https://lkml.org/lkml/2013/12/19/701

This one introduced the "problem" at my side.

>can you be more specific which is  the patch that introduced the
>regression, e.g if you apply them one by one, when things break?
>--
>To unsubscribe from this list: send the line "unsubscribe linux-pci" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
Richard Yang
Help you, Help me


  reply	other threads:[~2014-01-14  8:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14  6:22 mlx4_core probe error after applying Yinghai's patch Wei Yang
2014-01-14  7:55 ` Or Gerlitz
2014-01-14  8:27   ` Wei Yang
2014-01-14  8:39     ` Or Gerlitz
2014-01-14  8:52       ` Wei Yang [this message]
2014-01-14  8:50 ` Jack Morgenstein
2014-01-14  9:15   ` Wei Yang
2014-01-14 10:25     ` Jack Morgenstein
2014-01-14 11:19       ` Guo Chao
     [not found]       ` <52d51b4c.c413ec0a.290f.03c3SMTPIN_ADDED_BROKEN@mx.google.com>
2014-01-14 11:21         ` Jack Morgenstein
     [not found]   ` <20140114103712.GD27684@richard>
     [not found]     ` <20140114132340.50df7d6f@jpm-OptiPlex-GX620>
     [not found]       ` <52d52032.4981e00a.3dcc.ffff81fdSMTPIN_ADDED_BROKEN@mx.google.com>
     [not found]         ` <20140115094113.64ca756e@jpm-OptiPlex-GX620>
     [not found]           ` <1389772791.6933.84.camel@pasglop>
     [not found]             ` <52d653d3.8425e00a.76d0.1e60SMTPIN_ADDED_BROKEN@mx.google.com>
     [not found]               ` <20140115160204.24a44af0@jpm-OptiPlex-GX620>
     [not found]                 ` <20140116020946.GA8702@richard>
     [not found]                   ` <20140116021429.GB8702@richard>
2014-01-29  8:50                     ` Or Gerlitz
2014-01-30  7:08                       ` Wei Yang
2014-01-30  8:09                         ` Or Gerlitz
2014-01-14  8:54 ` Jack Morgenstein
2014-01-14  9:16   ` Wei Yang

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=20140114085244.GA27684@richard \
    --to=weiyang@linux.vnet.ibm.com \
    --cc=amirv@mellanox.com \
    --cc=benh@au1.ibm.com \
    --cc=bhelgaas@google.com \
    --cc=eugenia@mellanox.com \
    --cc=jackm@dev.mellanox.co.il \
    --cc=linux-pci@vger.kernel.org \
    --cc=ogerlitz@mellanox.com \
    --cc=shangw@linux.vnet.ibm.com \
    --cc=yan@linux.vnet.ibm.com \
    --cc=yinghai@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).