Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1200911
| From | Peter Zijlstra <peterz@infradead.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH RFC v1 1/4] perf: Introduce extended syscall error reporting |
| Date | 2015-08-05 17:40 +0200 |
| Message-ID | <pU8Xo-5uJ-21@gated-at.bofh.it> (permalink) |
| References | <pPJEd-4HJ-21@gated-at.bofh.it> <pPJEf-4HJ-37@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Fri, Jul 24, 2015 at 02:45:56PM +0300, Alexander Shishkin wrote:
> +#define __perf_err(__e, __c, __m) ({ \
> + static struct perf_err_site \
> + __attribute__ ((unused,__section__("__perf_err"))) \
> + __err_site = { \
> + .message = (__m), \
> + .owner = PERF_MODNAME, \
> + .code = __builtin_constant_p((__c)) ? \
> + (__c) : 0, \
> + }; \
> + (__e) = &__err_site; \
> +})
Why is __e an argument at all? Why not simply return &__err_site ?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next | Find similar | Unroll thread
Re: [PATCH RFC v1 1/4] perf: Introduce extended syscall error reporting Peter Zijlstra <peterz@infradead.org> - 2015-08-05 17:40 +0200
csiph-web