Re: [PATCH] kbuild: implement modules.order

>> I think, you forgot to free(3) the memory you calloc(3)'ed and
>> malloc(3)'ed above.
>
>It's a simple program where whole body is in main().  Why bother?
>What's the benefit of adding hash-table iterating free logic?
>

Personally, I think memory leaks are bugs. And we hate bugs. ;)

Regards.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: [PATCH] kbuild: implement modules.order
  - From: Tejun Heo <[email protected]>

References:
- [PATCH] kbuild: implement modules.order
  - From: Tejun Heo <[email protected]>
- Re: [PATCH] kbuild: implement modules.order
  - From: WANG Cong <[email protected]>
- Re: [PATCH] kbuild: implement modules.order
  - From: Tejun Heo <[email protected]>

Prev by Date: Re: sockets affected by IPsec always block (2.6.23)
Next by Date: Re: [PATCH] kbuild: implement modules.order
Previous by thread: Re: [PATCH] kbuild: implement modules.order
Next by thread: Re: [PATCH] kbuild: implement modules.order
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]