Christoph, you know I've got a question (may be it's stupid) - what a sense to discard UDF_I_* macroses? I mean as I see they don't slow down execution of the code... Cyrill - 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] UDF: check for allocated memory for inode data
- From: "Pekka Enberg" <[email protected]>
- Re: [PATCH] UDF: check for allocated memory for inode data
- References:
- [PATCH] UDF: check for allocated memory for inode data
- From: Cyrill Gorcunov <[email protected]>
- Re: [PATCH] UDF: check for allocated memory for inode data
- From: Andrew Morton <[email protected]>
- Re: [PATCH] UDF: check for allocated memory for inode data
- From: Christoph Hellwig <[email protected]>
- Re: [PATCH] UDF: check for allocated memory for inode data
- From: Cyrill Gorcunov <[email protected]>
- Re: [PATCH] UDF: check for allocated memory for inode data
- From: Christoph Hellwig <[email protected]>
- [PATCH] UDF: check for allocated memory for inode data
- Prev by Date: Re: [patch 3/3] clockevents: Fix resume logic - updated version
- Next by Date: Re: [PATCH 1/7] Freezer: Read PF_BORROWED_MM in a nonracy way
- Previous by thread: Re: [PATCH] UDF: check for allocated memory for inode data
- Next by thread: Re: [PATCH] UDF: check for allocated memory for inode data
- Index(es):
 |