From: Vipul Pandya <vipul@chelsio.com>
To: Roland Dreier <roland@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the infiniband tree
Date: Thu, 20 Dec 2012 15:28:16 +0530 [thread overview]
Message-ID: <50D2E138.7000700@chelsio.com> (raw)
In-Reply-To: <CAG4TOxPVc0tNeLhi3FF=K_UJpizh2OZgviT5WqqLvZsg-QEoNw@mail.gmail.com>
On 20-12-2012 05:52, Roland Dreier wrote:
> On Wed, Dec 19, 2012 at 2:44 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:
>>
>> In file included from drivers/scsi/csiostor/csio_wr.h:42:0,
>> from drivers/scsi/csiostor/csio_scsi.h:49,
>> from drivers/scsi/csiostor/csio_init.h:45,
>> from drivers/scsi/csiostor/csio_attr.c:45:
>> drivers/scsi/csiostor/t4fw_api_stor.h:43:6: error: nested redefinition of 'enum fw_retval'
>> drivers/scsi/csiostor/t4fw_api_stor.h:43:6: error: redeclaration of 'enum fw_retval'
>> drivers/net/ethernet/chelsio/cxgb4/t4fw_api.h:42:6: note: originally defined here
>> drivers/scsi/csiostor/t4fw_api_stor.h:48:2: error: redeclaration of enumerator 'FW_ENOEXEC'
>> drivers/net/ethernet/chelsio/cxgb4/t4fw_api.h:39:2: note: previous definition of 'FW_ENOEXEC' was here
>> drivers/scsi/csiostor/t4fw_api_stor.h:50:2: error: redeclaration of enumerator 'FW_ENOMEM'
>> drivers/net/ethernet/chelsio/cxgb4/t4fw_api.h:43:2: note: previous definition of 'FW_ENOMEM' was here
>> drivers/scsi/csiostor/t4fw_api_stor.h:58:2: error: redeclaration of enumerator 'FW_EADDRINUSE'
>> drivers/net/ethernet/chelsio/cxgb4/t4fw_api.h:44:2: note: previous definition of 'FW_EADDRINUSE' was here
>>
>> And several others similar.
>>
>> Caused by commit f65b56b15931 ("RDMA/cxgb4: Fix LE hash collision bug for
>> active open connection").
>
>
> Vipul, is the right fix to pull the full list of FW return values from
> t4fw_api_stor.h into t4fw_api.h as part of this patch (f65b56b15931)?
>
Yes, this is a correct way to fix this issue. I see that this change is
already done. Thanks for providing the fix.
next prev parent reply other threads:[~2012-12-20 9:58 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-19 22:44 linux-next: build failure after merge of the infiniband tree Stephen Rothwell
2012-12-19 22:44 ` Stephen Rothwell
[not found] ` <20121220094433.791d70e55ae5e3325a6190fc-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2012-12-20 0:22 ` Roland Dreier
2012-12-20 0:22 ` Roland Dreier
2012-12-20 9:58 ` Vipul Pandya [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
2014-12-16 1:47 Stephen Rothwell
2014-12-16 1:47 ` Stephen Rothwell
[not found] ` <20141216124750.153e3fdd-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2014-12-16 1:56 ` Roland Dreier
2014-12-16 1:56 ` Roland Dreier
2014-12-16 2:22 ` Roland Dreier
[not found] ` <CAG4TOxP9WFHALPb0y0eKFup6uhszXfd+hLcwZ98kZUVaR_9j4w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-12-16 10:57 ` Or Gerlitz
2014-12-16 10:57 ` Or Gerlitz
2012-08-16 1:44 Stephen Rothwell
2012-08-16 4:07 ` Roland Dreier
[not found] ` <CAG4TOxNLenjQxZNb7Rpm2G9RNBN77uWgEgfNXgoj+gLFdObuTg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-08-16 6:24 ` Or Gerlitz
2012-08-16 6:59 ` Stephen Rothwell
2012-08-16 6:59 ` Stephen Rothwell
2012-07-06 2:35 Stephen Rothwell
[not found] ` <20120706123555.949d8efb4de5c4df18fb1ec0-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2012-07-06 3:58 ` Roland Dreier
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
[not found] ` <20100709110427.c05987cc.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2010-07-09 3:46 ` Roland Dreier
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=50D2E138.7000700@chelsio.com \
--to=vipul@chelsio.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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.