From: Cyril Hrubis <chrubis@suse.cz>
To: Wanlong Gao <gaowanlong@cn.fujitsu.com>
Cc: "ltp-list@lists.sourceforge.net" <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [PATCH 2/2] Replace struct event_t with struct inotify_event
Date: Thu, 3 May 2012 14:46:06 +0200 [thread overview]
Message-ID: <20120503124606.GA9999@saboteur.suse.cz> (raw)
In-Reply-To: <4F854F21.5070208@cn.fujitsu.com>
Hi!
> >>>
> >>> Yeah... let me get back to you on that...
> >>
> >>
> >> Any update on this?
> >
> > I'm moving from CA to WA, but I'll try to get back to you sometime mid next week once I get settled in.
>
>
> That's great! I wonder what do CA and WA stand for?
I would guess that these are city names or something like that... ;)
And of course the patch is wrong, the event_t structure is used only to
record what have you done for sake of comparing the sequence to the
inotify events read later.
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2012-05-03 13:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 0:42 [LTP] [PATCH 2/2] Replace struct event_t with struct inotify_event Garrett Cooper
2012-04-05 1:39 ` Wanlong Gao
2012-04-05 2:10 ` Garrett Cooper
2012-04-11 2:53 ` Wanlong Gao
2012-04-11 9:18 ` Garrett Cooper
2012-04-11 9:30 ` Wanlong Gao
2012-05-03 12:46 ` Cyril Hrubis [this message]
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=20120503124606.GA9999@saboteur.suse.cz \
--to=chrubis@suse.cz \
--cc=gaowanlong@cn.fujitsu.com \
--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