public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH 1/2] Clean up inotify(7) wrappers
Date: Wed, 4 Apr 2012 21:52:55 -0400	[thread overview]
Message-ID: <201204042152.56885.vapier@gentoo.org> (raw)
In-Reply-To: <alpine.BSF.2.00.1204041735200.25027@toaster.local>


[-- Attachment #1.1: Type: Text/Plain, Size: 380 bytes --]

On Wednesday 04 April 2012 20:38:31 Garrett Cooper wrote:
> +/*
> + * ``junk`` is needed to make the macro function like a void argument
> + * function.
> + */
> +#define	myinotify_init(junk)	syscall(__NR_inotify_init)

you lost me.  how does this make it work like a (void) func ?  i think this 
should drop the "junk" and just do:
	#define myinotify_init() ...
-mike

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 274 bytes --]

------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev

[-- Attachment #3: Type: text/plain, Size: 155 bytes --]

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  parent reply	other threads:[~2012-04-05  1:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-05  0:38 [LTP] [PATCH 1/2] Clean up inotify(7) wrappers Garrett Cooper
2012-04-05  1:36 ` Wanlong Gao
2012-04-05  1:52 ` Mike Frysinger [this message]
2012-04-11  2:52   ` Wanlong Gao
2012-04-11  9:21     ` Garrett Cooper
2012-04-11  9:25       ` Wanlong Gao

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201204042152.56885.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=ltp-list@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox