From: Ingo Molnar <mingo@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Jiri Kosina <trivial@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] [trivial] perf: Spelling s/EACCESS/EACCES/
Date: Mon, 27 May 2019 17:15:42 +0200 [thread overview]
Message-ID: <20190527151542.GA50924@gmail.com> (raw)
In-Reply-To: <CAMuHMdV5TB4DRPuKkczYgCJ7+-yzEbnYp=TQydnK+3qmkPT4Tg@mail.gmail.com>
* Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> Hi Ingo,
>
> On Mon, May 27, 2019 at 4:12 PM Ingo Molnar <mingo@kernel.org> wrote:
> > * Geert Uytterhoeven <geert+renesas@glider.be> wrote:
> > > The correct spelling is EACCES:
> > >
> > > include/uapi/asm-generic/errno-base.h:#define EACCES 13 /* Permission denied */
> > >
> > > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
>
> > > --- a/include/linux/perf_event.h
> > > +++ b/include/linux/perf_event.h
> > > @@ -289,7 +289,7 @@ struct pmu {
> > > * -EBUSY -- @event is for this PMU but PMU temporarily unavailable
> > > * -EINVAL -- @event is for this PMU but @event is not valid
> > > * -EOPNOTSUPP -- @event is for this PMU, @event is valid, but not supported
> > > - * -EACCESS -- @event is for this PMU, @event is valid, but no privilidges
> > > + * -EACCES -- @event is for this PMU, @event is valid, but no privilidges
> > > *
> > > * 0 -- @event is for this PMU and valid
> > > *
> >
> >
> > Actually, -EACCES got typoed itself and survived due to historic reasons.
>
> Quite possible... Someone pointed out a while ago it is part of POSIX,
> hence it cannot be changed.
>
> Probably we can do "#define EACCESS EACCES"?
Don't think that's a good idea, nor is it necessary: it's only a comment,
right? But yeah, I guess we can do.
> > I think we can tolerate the 'typo' fixed in documentation, can we?
>
> IMHO we cannot, as e.g. "git grep -w" won't match both.
> Do you really want the documentation to differ from the implementation?
>
> > Also, the *far* bigger typo is, in the same line:
> >
> > s/privilidges
> > /privileges
>
> Thanks, that one didn't show up with "git grep -w EACCESS" ;-)
> Will send v2...
:-)
Thanks,
Ingo
prev parent reply other threads:[~2019-05-27 15:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 12:23 [PATCH] [trivial] perf: Spelling s/EACCESS/EACCES/ Geert Uytterhoeven
2019-05-27 14:12 ` Ingo Molnar
2019-05-27 14:27 ` Geert Uytterhoeven
2019-05-27 15:15 ` Ingo Molnar [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=20190527151542.GA50924@gmail.com \
--to=mingo@kernel.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=trivial@kernel.org \
/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.