public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: chrubis@suse.cz
To: Wang Xiaoguang <wangxg.fnst@cn.fujitsu.com>
Cc: Garrett Cooper <yanegomi@gmail.com>,
	LTP <ltp-list@lists.sourceforge.net>,
	Mike Frysinger <vapier@gentoo.org>
Subject: Re: [LTP] [PATCH 1/3] pthread_rwlock_rdlock:2-1: do not test on glibc
Date: Tue, 28 Jan 2014 14:23:47 +0100	[thread overview]
Message-ID: <20140128132346.GB5824@rei> (raw)
In-Reply-To: <52D5F124.3090204@cn.fujitsu.com>

Hi!
> 
> Whether there are some new progress about these three cases?
> 

Sorry, not yet, but I keep it on my TODO.

-- 
Cyril Hrubis
chrubis@suse.cz

------------------------------------------------------------------------------
WatchGuard Dimension instantly turns raw network data into actionable 
security intelligence. It gives you real-time visual feedback on key
security issues and trends.  Skip the complicated setup - simply import
a virtual appliance and go from zero to informed in seconds.
http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

      parent reply	other threads:[~2014-01-28 13:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1374807380-20319-1-git-send-email-gaowanlong@cn.fujitsu.com>
2013-07-26  7:07 ` [LTP] [PATCH 1/3] pthread_rwlock_rdlock:2-1: do not test on glibc Jan Stancek
2013-07-26  7:52   ` Wanlong Gao
2013-07-26  8:28     ` Jan Stancek
2013-07-26  8:30       ` Wanlong Gao
2013-07-31 11:16 ` chrubis
     [not found]   ` <52836390.5080104@cn.fujitsu.com>
2013-11-13 15:13     ` chrubis
     [not found]       ` <52D5F124.3090204@cn.fujitsu.com>
2014-01-28 13:23         ` chrubis [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=20140128132346.GB5824@rei \
    --to=chrubis@suse.cz \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=vapier@gentoo.org \
    --cc=wangxg.fnst@cn.fujitsu.com \
    --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