public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH 2/2] Replace struct event_t with struct inotify_event
Date: Wed, 11 Apr 2012 10:53:06 +0800	[thread overview]
Message-ID: <4F84F212.9070408@cn.fujitsu.com> (raw)
In-Reply-To: <CAGH67wRSAKEkn=MNn2HHivnPNjuP_tqE8+S1-ND_Z69VrBm9Ow@mail.gmail.com>

On 04/05/2012 10:10 AM, Garrett Cooper wrote:

> On Wed, Apr 4, 2012 at 6:39 PM, Wanlong Gao <gaowanlong@cn.fujitsu.com> wrote:
>> On 04/05/2012 08:42 AM, Garrett Cooper wrote:
>>
>>> Replace struct event_t with struct inotify_event
>>>
>>> Also do some minor whitespace cleanup while I'm
>>> in the neighborhood.
>>
>> there's something wrong with this patch, please take a look at the ".name".
> 
> Yeah... let me get back to you on that...


Any update on this?

Thanks,
Wanlong Gao

> -Garrett
> 



------------------------------------------------------------------------------
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
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2012-04-11  2:54 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 [this message]
2012-04-11  9:18       ` Garrett Cooper
2012-04-11  9:30         ` Wanlong Gao
2012-05-03 12:46           ` Cyril Hrubis

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=4F84F212.9070408@cn.fujitsu.com \
    --to=gaowanlong@cn.fujitsu.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=yanegomi@gmail.com \
    /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