From: Andrew Morton <akpm@osdl.org>
To: Hal Rosenstock <halr@voltaire.com>
Cc: linux-kernel@vger.kernel.org, openib-general@openib.org,
rolandd@cisco.com
Subject: Re: [PATCH 0/29v2] InfiniBand core update
Date: Tue, 12 Jul 2005 15:38:59 -0700 [thread overview]
Message-ID: <20050712153859.7b757c4a.akpm@osdl.org> (raw)
In-Reply-To: <1121206549.4382.10.camel@hal.voltaire.com>
Hal Rosenstock <halr@voltaire.com> wrote:
>
> On Mon, 2005-07-11 at 23:11, Andrew Morton wrote:
> > Well I was asking. Do you guys think that this material is appropriate to
> > and safe enough for 2.6.13?
>
> I used your versions of the patches (Tom's ucm one is needed and you
> added that). I also back ported the trailing whitespace elimination
> changes.
>
> I just completed a regression test including uCM, CM, RMPP, OpenSM,
> IPoIB and it looks good to me.
>
OK, well the timing of a merge is mainly up to you guys, especially as the
subsystem is pretty raw and you're the only people who use it ;)
Two things from a quick scan:
a) In many places the patch does
if (p)
kfree(p);
But kfree(0) is permitted. The cleanup police will be after you at
some stage - it'd be best to fix those things up immediately.
b) The patch exports a ton of symbols to non-GPL modules:
+EXPORT_SYMBOL(ib_create_ah_from_wc);
+EXPORT_SYMBOL(ib_modify_mad);
+EXPORT_SYMBOL(ib_create_send_mad);
+EXPORT_SYMBOL(ib_free_send_mad);
+EXPORT_SYMBOL(ib_coalesce_recv_mad);
+EXPORT_SYMBOL(ib_sa_service_rec_query);
+EXPORT_SYMBOL(ib_create_cm_id);
+EXPORT_SYMBOL(ib_destroy_cm_id);
+EXPORT_SYMBOL(ib_cm_listen);
+EXPORT_SYMBOL(ib_send_cm_req);
+EXPORT_SYMBOL(ib_send_cm_rep);
+EXPORT_SYMBOL(ib_send_cm_rtu);
+EXPORT_SYMBOL(ib_send_cm_dreq);
+EXPORT_SYMBOL(ib_send_cm_drep);
+EXPORT_SYMBOL(ib_send_cm_rej);
+EXPORT_SYMBOL(ib_send_cm_mra);
+EXPORT_SYMBOL(ib_send_cm_lap);
+EXPORT_SYMBOL(ib_send_cm_apr);
+EXPORT_SYMBOL(ib_send_cm_sidr_req);
+EXPORT_SYMBOL(ib_send_cm_sidr_rep);
+EXPORT_SYMBOL(ib_cm_establish);
+EXPORT_SYMBOL(ib_cm_init_qp_attr);
Why?
next prev parent reply other threads:[~2005-07-12 22:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 19:30 [PATCH 0/29v2] InfiniBand core update Hal Rosenstock
2005-07-11 19:53 ` David S. Miller
2005-07-12 0:05 ` Andrew Morton
2005-07-12 2:45 ` Hal Rosenstock
2005-07-12 3:11 ` Andrew Morton
2005-07-12 9:43 ` Hal Rosenstock
2005-07-12 22:15 ` Hal Rosenstock
2005-07-12 22:38 ` Andrew Morton [this message]
2005-07-12 22:51 ` Hal Rosenstock
2005-07-12 3:12 ` David S. Miller
2005-07-12 9:11 ` Hal Rosenstock
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=20050712153859.7b757c4a.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=halr@voltaire.com \
--cc=linux-kernel@vger.kernel.org \
--cc=openib-general@openib.org \
--cc=rolandd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox