public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] fs/ftest/ftest06.c: Fix too small name string and	related failure
Date: Fri, 24 Aug 2018 04:34:08 -0400 (EDT)	[thread overview]
Message-ID: <91481629.42296391.1535099648037.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20180824014624.26667-1-zhe.he@windriver.com>



----- Original Message -----
> The name string is too small to contain normal full path names and causes
> the following failure.
> 
> "ftest06     2  TFAIL  :  ftest06.c:223: Can't chdir(): errno=ENOENT(2): No
> such file or directory"
> 
> Signed-off-by: He Zhe <zhe.he@windriver.com>

Pushed.

Thanks,
Jan

  reply	other threads:[~2018-08-24  8:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-24  1:46 [LTP] [PATCH] fs/ftest/ftest06.c: Fix too small name string and related failure He Zhe
2018-08-24  8:34 ` Jan Stancek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-08-24  1:59 He Zhe
2018-08-22 16:34 zhe.he
2018-08-23 14:21 ` 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=91481629.42296391.1535099648037.JavaMail.zimbra@redhat.com \
    --to=jstancek@redhat.com \
    --cc=ltp@lists.linux.it \
    /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