public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
* Re: linux-next: Tree for Nov 16 (infiniband: ib_srpt.c)
       [not found] ` <20111116133342.3eb15cac16f4c081dc6ed009-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
@ 2011-11-17  2:34   ` Randy Dunlap
  2011-11-17 18:51     ` Bart Van Assche
  0 siblings, 1 reply; 2+ messages in thread
From: Randy Dunlap @ 2011-11-17  2:34 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: linux-next-u79uwXL29TY76Z2rM5mHXA, LKML, Linux RDMA,
	Bart Van Assche

On 11/15/2011 06:33 PM, Stephen Rothwell wrote:
> Hi all,


When CONFIG_BUG is not enabled:

next-2011-1116/drivers/infiniband/ulp/srpt/ib_srpt.c: In function 'srpt_cm_dreq_recv':
next-2011-1116/drivers/infiniband/ulp/srpt/ib_srpt.c:2761:3: error: implicit declaration of function '__WARN'


jbd2 has a similar issue (still unpatched).  One of the comments in that thread
was that ext4 probably should use WARN_ON() instead of __WARN().

Or (Arnd said):
Hmm, my feeling is that we shouldn't do that either, and that jbd2 should
be changed. If we want a function that does what __WARN() does today, we
should probably make a conscious decision about what we want it to be called
and not have it start with "__". <end Arnd>


-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: linux-next: Tree for Nov 16 (infiniband: ib_srpt.c)
  2011-11-17  2:34   ` linux-next: Tree for Nov 16 (infiniband: ib_srpt.c) Randy Dunlap
@ 2011-11-17 18:51     ` Bart Van Assche
  0 siblings, 0 replies; 2+ messages in thread
From: Bart Van Assche @ 2011-11-17 18:51 UTC (permalink / raw)
  To: Randy Dunlap; +Cc: Stephen Rothwell, linux-next, LKML, Linux RDMA

On Thu, Nov 17, 2011 at 3:34 AM, Randy Dunlap <rdunlap@xenotime.net> wrote:
> On 11/15/2011 06:33 PM, Stephen Rothwell wrote:
>> Hi all,
>
>
> When CONFIG_BUG is not enabled:
>
> next-2011-1116/drivers/infiniband/ulp/srpt/ib_srpt.c: In function 'srpt_cm_dreq_recv':
> next-2011-1116/drivers/infiniband/ulp/srpt/ib_srpt.c:2761:3: error: implicit declaration of function '__WARN'
>
>
> jbd2 has a similar issue (still unpatched).  One of the comments in that thread
> was that ext4 probably should use WARN_ON() instead of __WARN().
>
> Or (Arnd said):
> Hmm, my feeling is that we shouldn't do that either, and that jbd2 should
> be changed. If we want a function that does what __WARN() does today, we
> should probably make a conscious decision about what we want it to be called
> and not have it start with "__". <end Arnd>

Thanks for reporting this. The __WARN() statements in ib_srpt are
present in code paths that should never be reached. I'll post a patch
that addresses the build failure.

Bart.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2011-11-17 18:51 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <20111116133342.3eb15cac16f4c081dc6ed009@canb.auug.org.au>
     [not found] ` <20111116133342.3eb15cac16f4c081dc6ed009-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2011-11-17  2:34   ` linux-next: Tree for Nov 16 (infiniband: ib_srpt.c) Randy Dunlap
2011-11-17 18:51     ` Bart Van Assche

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox