linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Or Gerlitz <ogerlitz@mellanox.com>
To: Roland Dreier <roland@kernel.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	Haggai Eran <haggaie@mellanox.com>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Yevgeny Petrilin <yevgenyp@mellanox.com>,
	Amir Vadai <amirv@mellanox.com>
Subject: Re: linux-next: build failure after merge of the infiniband tree
Date: Tue, 16 Dec 2014 12:57:37 +0200	[thread overview]
Message-ID: <54901021.9020205@mellanox.com> (raw)
In-Reply-To: <CAG4TOxP9WFHALPb0y0eKFup6uhszXfd+hLcwZ98kZUVaR_9j4w@mail.gmail.com>

On 12/16/2014 3:56 AM, Roland Dreier wrote:
> On Mon, Dec 15, 2014 at 5:47 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>> Hi all,
>>
>> After merging the infiniband tree, today's linux-next build (x86_64
>> allmodconfig) failed like this:
>>
>> drivers/infiniband/hw/mlx5/main.c: In function 'mlx5_ib_query_device':
>> drivers/infiniband/hw/mlx5/main.c:248:34: error: 'MLX5_DEV_CAP_FLAG_ON_DMND_PG' undeclared (first use in this function)
>>    if (dev->mdev->caps.gen.flags & MLX5_DEV_CAP_FLAG_ON_DMND_PG)
>>                                    ^
>> [...]
>> Really?  Code added half way though the merge window not even build
>> tested?
> It's not quite as bad as it seems.  The infiniband tree itself builds,
> the problem is the merged tree.
>
> The Mellanox guys merged the "cleanup"

Hi Roland,

So shit happens... Eli is away this week, but it's clear that this 
portion of the cleanup
was terribly wrongand done by mistake, sorry for that and thanks for 
addressing quickly.

Or.

>
> commit 0c7aac854f52
> Author: Eli Cohen <eli@dev.mellanox.co.il>
> Date:   Tue Dec 2 02:26:14 2014
>
>      net/mlx5_core: Remove unused dev cap enum fields
>
>      These enumerations are not used so remove them.
>
>      Signed-off-by: Eli Cohen <eli@mellanox.com>
>      Signed-off-by: David S. Miller <davem@davemloft.net>
>
> through davem's tree, and then went ahead and used at least
> MLX5_DEV_CAP_FLAG_ON_DMND_PG (which that patch removes) in patches
> they merged through my tree.
>
> I'll add a partial revert of that patch to my tree to get back the
> now-used enum values.
>
>   - R.
>

  parent reply	other threads:[~2014-12-16 11:14 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-16  1:47 linux-next: build failure after merge of the infiniband tree Stephen Rothwell
2014-12-16  1:56 ` Roland Dreier
2014-12-16  2:22   ` Roland Dreier
2014-12-16 10:57   ` Or Gerlitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-02-18  2:32 Stephen Rothwell
2015-02-18  3:01 ` Roland Dreier
2012-12-19 22:44 Stephen Rothwell
2012-12-20  0:22 ` Roland Dreier
2012-12-20  9:58   ` Vipul Pandya
2012-08-16  1:44 Stephen Rothwell
2012-08-16  4:07 ` Roland Dreier
2012-08-16  6:59   ` Stephen Rothwell
2012-07-06  2:35 Stephen Rothwell
2012-07-06  3:58 ` Roland Dreier
2012-07-06  6:31   ` Hefty, Sean
2012-05-21  2:05 Stephen Rothwell
2012-05-21 14:04 ` Vipul Pandya
2012-05-21 16:03   ` Roland Dreier
2011-10-11  3:49 Stephen Rothwell
2010-07-09  1:04 Stephen Rothwell
2010-07-09  3:05 ` Ben Hutchings
2010-07-09  3:46 ` Roland Dreier
2010-07-09  6:16   ` Stephen Rothwell

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=54901021.9020205@mellanox.com \
    --to=ogerlitz@mellanox.com \
    --cc=amirv@mellanox.com \
    --cc=haggaie@mellanox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=roland@kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=yevgenyp@mellanox.com \
    /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).