Re: [ofa-general] Re: [PATCH v2] iw_cxgb3: Support "iwarp-only" interfaces to avoid 4-tuple conflicts.
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Date: Mon, 17 Sep 2007 20:17:07 +0400
On Mon, Sep 17, 2007 at 09:09:06AM -0700, Sean Hefty (mshefty@xxxxxxxxxxxxxxxx) wrote:
+ addr = kmalloc(sizeof *addr, GFP_KERNEL);
As a small nitpick: this wants to be sizeof(struct in_ifaddr)
See chapter 14 of CodingStyle document. kmalloc(sizeof *addr... is correct.
Come on, do not start a flame war about how parameters into kmalloc
should be provided - there are much more serious issues unresolved yes. It
does help grepping the code, but if you feel that this is a serious threat,
then use your preferred way.
--
Evgeniy Polyakov
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- [PATCH v2] iw_cxgb3: Support "iwarp-only" interfaces to avoid 4-tuple conflicts.
- From: Steve Wise
- Re: [PATCH v2] iw_cxgb3: Support "iwarp-only" interfaces to avoid 4-tuple conflicts.
- From: Evgeniy Polyakov
- Re: [PATCH v2] iw_cxgb3: Support "iwarp-only" interfaces to avoid 4-tuple conflicts.
- From: Steve Wise
- Re: [ofa-general] Re: [PATCH v2] iw_cxgb3: Support "iwarp-only" interfaces to avoid 4-tuple conflicts.
- From: Sean Hefty
- [PATCH v2] iw_cxgb3: Support "iwarp-only" interfaces to avoid 4-tuple conflicts.
- Prev by Date: Re: [PATCH 048/104] KVM: Add and use pr_unimpl for standard formatting of unimplemented features
- Next by Date: Re: Wasting our Freedom
- Previous by thread: Re: [ofa-general] Re: [PATCH v2] iw_cxgb3: Support "iwarp-only" interfaces to avoid 4-tuple conflicts.
- Next by thread: [PATCH] i386: Compaq EVO N800c needs PCI bus renumbering
- Index(es):