Re: [linux-usb-devel] [PATCH] usb: microtek possible memleak fix

Hello, 

> Ist there a reason you are replacing at least somewhat descriptive labels
> with numbers?

Yes.

To me these numbers speak more than not really descriptive labels like
out_kfree out_kfree2 etc. I look at the code and see the flow. The most
important thing here is the order in which the resources are allocated and
if something goes wrong deallocated. Hence the numbers.

Anyway if that's a problem I can rewrite it.

-- 
Regards,

	Mariusz Kozlowski
-
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/

---

• References:
  • [PATCH] usb: microtek possible memleak fix
    • From: Mariusz Kozlowski <[email protected]>

• Prev by Date: Re: 2.6.19-rc6-rt0, -rt YUM repository
• Next by Date: [PATCH 2/2]: HVCS char driver janitoring: rm compiler warnings
• Previous by thread: [PATCH] usb: microtek possible memleak fix
• Next by thread: Re: [linux-usb-devel] [PATCH] usb: microtek possible memleak fix [second try]
• 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]