From: Cyril Hrubis <chrubis@suse.cz>
To: zhe.he@windriver.com
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] fs/ftest/ftest06.c: Fix too small name string and related failure
Date: Thu, 23 Aug 2018 16:21:30 +0200 [thread overview]
Message-ID: <20180823142130.GA16435@rei> (raw)
In-Reply-To: <1534955646-104428-1-git-send-email-zhe.he@windriver.com>
Hi!
This mailing list has been replaced by ltp@lists.linux.it long time ago,
please send patches to the new list instead.
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2018-08-23 14:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-22 16:34 [LTP] [PATCH] fs/ftest/ftest06.c: Fix too small name string and related failure zhe.he
2018-08-23 14:21 ` Cyril Hrubis [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-08-24 1:46 He Zhe
2018-08-24 8:34 ` Jan Stancek
2018-08-24 1:59 He Zhe
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=20180823142130.GA16435@rei \
--to=chrubis@suse.cz \
--cc=ltp-list@lists.sourceforge.net \
--cc=zhe.he@windriver.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