All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bryan O'Sullivan" <bos@pathscale.com>
To: Roland Dreier <rdreier@cisco.com>
Cc: akpm@osdl.org, greg@kroah.com, linux-kernel@vger.kernel.org,
	openib-general@openib.org
Subject: Re: [PATCH 0 of 18] ipath driver - for inclusion in 2.6.17
Date: Fri, 24 Mar 2006 11:11:55 -0800	[thread overview]
Message-ID: <1143227515.30626.43.camel@serpentine.pathscale.com> (raw)
In-Reply-To: <ada4q1nr7pu.fsf@cisco.com>

On Fri, 2006-03-24 at 10:57 -0800, Roland Dreier wrote:

> It's customary to work through subsystem maintainers to merge new drivers...

OK, I'll feed patches to you, then.  No inconvenience intended.

Thanks for applying the patches.

> I fixed a couple of minor whitespace problems and made it actually
> build (hint: the constant RDMA_NODE_IB_CA does not exist in the
> upstream kernel).

Oops.

> It seems you need to fix up your Kconfig dependencies somewhat.

Will do.

>   On
> x86_64 allnoconfig + CONFIG_PCI=y, CONFIG_PCI_MSI=y,
> CONFIG_INFINIBAND=y, CONFIG_IPATH_CORE=y, CONFIG_INFINIBAND_IPATH=y, I get:
> 
>     drivers/built-in.o: In function `ipath_free_pddata': undefined reference to `kfree_skb'
>     drivers/built-in.o: In function `ipath_alloc_skb': undefined reference to `__alloc_skb'
>     drivers/built-in.o: In function `ipath_kreceive': undefined reference to `skb_over_panic'
>     drivers/built-in.o: In function `ipath_init_chip': undefined reference to `kfree_skb'

Would your preference be to slap #ifdefs around those, or to just
require CONFIG_NET in Kconfig?  The core driver should work fine without
any kernel-level networking support, so I suppose the former makes more
sense.

> It also looks like there are a few problems on ia64:
> 
>     drivers/infiniband/hw/ipath/ipath_verbs.c:733: warning: implicit declaration of function `atomic_set_mask'
>     drivers/infiniband/hw/ipath/ipath_verbs.c:734: warning: implicit declaration of function `atomic_clear_mask'
>     drivers/infiniband/hw/ipath/ipath_verbs.c: In function `show_stats':
>     drivers/infiniband/hw/ipath/ipath_verbs.c:1184: warning: long long unsigned int format, u64 arg (arg 4)
>     drivers/infiniband/hw/ipath/ipath_verbs.c:1184: warning: long long unsigned int format, u64 arg (arg 5)
>     drivers/infiniband/hw/ipath/ipath_pe800.c: In function `ipath_pe_handle_hwerrors':
>     drivers/infiniband/hw/ipath/ipath_pe800.c:353: warning: long long unsigned int format, long unsigned int arg (arg 5)
>     drivers/infiniband/hw/ipath/ipath_pe800.c:353: warning: long long unsigned int format, long unsigned int arg (arg 3)

That's going to be interesting to test, because I don't have any ia64
hardware to even compile on.  I have tested on x86_64 and powerpc, so
this seems like an arch-level header deficiency.  Any idea what to do
about it?

> I also wouldn't say the driver is sparse clean.

I've been building with C=1 for months.  I'll see if I can figure out
why you're getting such different results.

	<b


  reply	other threads:[~2006-03-24 19:11 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-24  4:41 [PATCH 0 of 18] ipath driver - for inclusion in 2.6.17 Bryan O'Sullivan
2006-03-24  4:41 ` [PATCH 1 of 18] ipath - core device driver Bryan O'Sullivan
2006-03-24  4:41 ` [PATCH 2 of 18] ipath - core driver header files Bryan O'Sullivan
2006-03-24  4:41 ` [PATCH 3 of 18] ipath - copy and send routines for sending an skb Bryan O'Sullivan
2006-03-24  4:41 ` [PATCH 4 of 18] ipath - support for HyperTransport devices Bryan O'Sullivan
2006-03-24  4:41 ` [PATCH 5 of 18] ipath - support for PCI Express devices Bryan O'Sullivan
2006-03-24  4:41 ` [PATCH 6 of 18] ipath - chip initialisation code Bryan O'Sullivan
2006-03-24  4:41 ` [PATCH 7 of 18] ipath - misc driver support code Bryan O'Sullivan
2006-03-24  4:41 ` [PATCH 8 of 18] ipath - sysfs and ipathfs support for core driver Bryan O'Sullivan
2006-03-24  4:41 ` [PATCH 9 of 18] ipath - char devices for diagnostics and lightweight subnet management Bryan O'Sullivan
2006-03-24  4:41 ` [PATCH 10 of 18] ipath - support for userspace apps using core driver Bryan O'Sullivan
2006-03-24  4:41 ` [PATCH 11 of 18] ipath - layering interfaces used by higher-level driver code Bryan O'Sullivan
2006-03-24  4:41 ` [PATCH 12 of 18] ipath - infiniband header files Bryan O'Sullivan
2006-03-24  4:41 ` [PATCH 13 of 18] ipath - infiniband UC and UD protocol support Bryan O'Sullivan
2006-03-24  4:41 ` [PATCH 14 of 18] ipath - infiniband RC " Bryan O'Sullivan
2006-03-24  4:41 ` [PATCH 15 of 18] ipath - misc infiniband code, part 1 Bryan O'Sullivan
2006-03-24  4:41 ` [PATCH 16 of 18] ipath - misc infiniband code, part 2 Bryan O'Sullivan
2006-03-24  4:41 ` [PATCH 17 of 18] ipath - infiniband verbs support Bryan O'Sullivan
2006-03-24  4:41 ` [PATCH 18 of 18] ipath - kbuild infrastructure Bryan O'Sullivan
2006-03-24 18:57 ` [PATCH 0 of 18] ipath driver - for inclusion in 2.6.17 Roland Dreier
2006-03-24 19:11   ` Bryan O'Sullivan [this message]
2006-03-24 20:57     ` Muli Ben-Yehuda
2006-03-24 21:19     ` [openib-general] " Roland Dreier
2006-03-24 22:33       ` Bryan O'Sullivan
2006-03-24 23:21         ` Roland Dreier
2006-03-25  0:03           ` Bryan O'Sullivan

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=1143227515.30626.43.camel@serpentine.pathscale.com \
    --to=bos@pathscale.com \
    --cc=akpm@osdl.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openib-general@openib.org \
    --cc=rdreier@cisco.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 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.