All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Avinesh Kumar <akumar@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] open08.c: Docparse format and rewording of description
Date: Mon, 11 Jul 2022 08:24:52 +0200	[thread overview]
Message-ID: <YsvCNJpex4jwQYYH@pevik> (raw)
In-Reply-To: <20220709165000.27830-1-akumar@suse.de>

Hi Avinesh,

> + * Verify that open() fails with:
Here needs to be blank line otherwise the result would be wrongly formatted:

Verify that open() fails with: - EEXIST when pathname already exists and O_CREAT and O_EXCL were used - EISDIR when pathname refers to a directory and the access requested involved writing - ENOTDIR when O_DIRECTORY was specified and pathname was not a directory - ENAMETOOLONG when pathname was too long - EACCES when requested access to the file is not allowed - EFAULT when pathname points outside the accessible address space

Please next time verify the result (cd metadata && make && $BROWSER ../docparse/*.html

Merged with this fix, removed docs and space behind #define.

Kind regards,
Petr

> + * - EEXIST when pathname already exists and O_CREAT and O_EXCL were used.
> + * - EISDIR when pathname refers to a directory and the access requested
> + * involved writing.
> + * - ENOTDIR when O_DIRECTORY was specified and pathname was not a directory.
> + * - ENAMETOOLONG when pathname was too long.
> + * - EACCES when requested access to the file is not allowed.
> + * - EFAULT when pathname points outside the accessible address space.
>   */

>  #define _GNU_SOURCE		/* for O_DIRECTORY */

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

      reply	other threads:[~2022-07-11  6:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-09 16:49 [LTP] [PATCH] open08.c: Docparse format and rewording of description Avinesh Kumar
2022-07-11  6:24 ` Petr Vorel [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=YsvCNJpex4jwQYYH@pevik \
    --to=pvorel@suse.cz \
    --cc=akumar@suse.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.