Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\]\s+get\s+rid\s+of\s+fname\[\]\s+for\s+tracing\s+functions\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\]\s+get\s+rid\s+of\s+fname\[\]\s+for\s+tracing\s+functions\s*$/: 8 ]

Total 8 documents matching your query.

1. [PATCH] get rid of fname[] for tracing functions (score: 1): Author: Eric Sandeen <sandeen@xxxxxxxxxxx>; Date: Tue, 06 Mar 2007 21:18:11 -0600; this gets rid of the static char fname[] = "xfs_iextents_copy"; ugliness littered in the bmap code for tracing, and instead just uses gcc's __FUNCTION__, which never gets out of sync with the actual; /archives/xfs/2007-03/msg00020.html (75,881 bytes)
2. Re: [PATCH] get rid of fname[] for tracing functions (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Wed, 7 Mar 2007 08:27:53 +0000; Very nice. I might hear some people to scream that we should use the C99 __func__ and not the __FUNCTION__ gccism, but __FUNCTION__ is what the rest of the Linux kernel uses, and can be emulated with; /archives/xfs/2007-03/msg00021.html (9,028 bytes)
3. Re: [PATCH] get rid of fname[] for tracing functions (score: 1): Author: Eric Sandeen <sandeen@xxxxxxxxxxx>; Date: Wed, 07 Mar 2007 08:34:50 -0600; Christoph Hellwig wrote: the vn tracing could probably get a similar treatment, so that every call to vn_trace_foo wouldn't have to include a function name and a __builtin_return_address, but could b; /archives/xfs/2007-03/msg00028.html (8,538 bytes)
4. Re: [PATCH] get rid of fname[] for tracing functions (score: 1): Author: Eric Sandeen <sandeen@xxxxxxxxxxx>; Date: Fri, 16 Mar 2007 21:27:10 -0500; slight quilt misfire... here's an updated version -- Get rid of fname[] arrays for tracing code, and just use gcc's __FUNCTION__ instead. xfs_alloc.c | 53 ++-- xfs_bmap.c | 266 ++++++++++++++++++++++; /archives/xfs/2007-03/msg00112.html (76,395 bytes)
5. [PATCH] get rid of fname[] for tracing functions (score: 1): Author: Eric Sandeen <sandeen@xxxxxxxxxxx>; Date: Tue, 06 Mar 2007 21:18:11 -0600; this gets rid of the static char fname[] = "xfs_iextents_copy"; ugliness littered in the bmap code for tracing, and instead just uses gcc's __FUNCTION__, which never gets out of sync with the actual; /archives/xfs/2007-03/msg00250.html (75,881 bytes)
6. Re: [PATCH] get rid of fname[] for tracing functions (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Wed, 7 Mar 2007 08:27:53 +0000; Very nice. I might hear some people to scream that we should use the C99 __func__ and not the __FUNCTION__ gccism, but __FUNCTION__ is what the rest of the Linux kernel uses, and can be emulated with; /archives/xfs/2007-03/msg00251.html (9,028 bytes)
7. Re: [PATCH] get rid of fname[] for tracing functions (score: 1): Author: Eric Sandeen <sandeen@xxxxxxxxxxx>; Date: Wed, 07 Mar 2007 08:34:50 -0600; Christoph Hellwig wrote: the vn tracing could probably get a similar treatment, so that every call to vn_trace_foo wouldn't have to include a function name and a __builtin_return_address, but could b; /archives/xfs/2007-03/msg00258.html (8,538 bytes)
8. Re: [PATCH] get rid of fname[] for tracing functions (score: 1): Author: Eric Sandeen <sandeen@xxxxxxxxxxx>; Date: Fri, 16 Mar 2007 21:27:10 -0500; slight quilt misfire... here's an updated version -- Get rid of fname[] arrays for tracing code, and just use gcc's __FUNCTION__ instead. xfs_alloc.c | 53 ++-- xfs_bmap.c | 266 ++++++++++++++++++++++; /archives/xfs/2007-03/msg00342.html (76,395 bytes)

Current List: 1 - 8
Page: [1]