LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: colin.king@canonical.com, jk@ozlabs.org,
Jonathan Corbet <corbet@lwn.net>, Dave Airlie <airlied@linux.ie>,
maarten.lankhorst@linux.intel.com, maxime.ripard@bootlin.com,
sean@poorly.run, linuxppc-dev@lists.ozlabs.org,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
kernel-janitors@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Documentation: fix spelling mistake, EACCESS -> EACCES
Date: Fri, 26 Oct 2018 11:40:09 -0700 [thread overview]
Message-ID: <20181026184009.GV25444@bombadil.infradead.org> (raw)
In-Reply-To: <CANiq72nFZS=3KGaQpGjRbprh8HTBiTcSpxScE2uacDmg-xqDGA@mail.gmail.com>
On Fri, Oct 26, 2018 at 08:20:12PM +0200, Miguel Ojeda wrote:
> On Fri, Oct 26, 2018 at 7:27 PM Colin King <colin.king@canonical.com> wrote:
> >
> > From: Colin Ian King <colin.king@canonical.com>
> >
> > Trivial fix to a spelling mistake of the error access name EACCESS,
> > rename to EACCES
>
> ? It is not a typo, it is the name of the error (POSIX). Same thing
> for the rest of the patches.
Are you sure? From open(2):
EACCES The requested access to the file is not allowed, or search per‐
mission is denied for one of the directories in the path prefix
of pathname, or the file did not exist yet and write access to
the parent directory is not allowed. (See also path_resolu‐
tion(7).)
include/uapi/asm-generic/errno-base.h:#define EACCES 13 /* Permission denied */
next prev parent reply other threads:[~2018-10-26 18:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 17:25 Colin King
2018-10-26 18:20 ` Miguel Ojeda
2018-10-26 18:40 ` Matthew Wilcox [this message]
2018-10-26 18:53 ` Miguel Ojeda
2018-10-26 18:54 ` Miguel Ojeda
2018-11-07 22:31 ` Jonathan Corbet
2018-11-08 0:38 ` Jeremy Kerr
2018-11-12 12:57 ` Michael Ellerman
2018-11-12 20:15 ` Geoff Levand
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=20181026184009.GV25444@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=airlied@linux.ie \
--cc=colin.king@canonical.com \
--cc=corbet@lwn.net \
--cc=jk@ozlabs.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=maxime.ripard@bootlin.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=sean@poorly.run \
--subject='Re: [PATCH] Documentation: fix spelling mistake, EACCESS -> EACCES' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).