From: Jonathan Corbet <corbet@lwn.net>
To: Federico Vaga <federico.vaga@vaga.pv.it>
Cc: Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] doc:lock: remove reference to clever use of read-write lock
Date: Mon, 2 Sep 2019 14:21:33 -0600 [thread overview]
Message-ID: <20190902142133.37e106af@lwn.net> (raw)
In-Reply-To: <4627860.yBeiQmOknq@harkonnen>
On Mon, 02 Sep 2019 21:19:24 +0200
Federico Vaga <federico.vaga@vaga.pv.it> wrote:
> > > I am not used to the mathematical English jargon. It make sense, but then
> > > I
> > > would replace it with "If and only if": for clarity.
> >
> > While it's used in a number of places and it's pretty common wording
> > overall in the literature, I agree that we should probably change this in
> > locking API user facing documentation.
>
> I would say not only in locking/. The argument is valid for the entire
> Documentation/. I wait for Jon's opinion before proceeding.
I don't really have a problem with "iff"; it doesn't seem like *that*
obscure a term to me. But if you want spell it out, I guess I don't have
a problem with that. We can change it - iff you send a patch to do it :)
Thanks,
jon
next prev parent reply other threads:[~2019-09-02 20:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-31 13:41 [PATCH] doc:lock: remove reference to clever use of read-write lock Federico Vaga
2019-08-31 14:43 ` Jonathan Corbet
2019-09-02 7:01 ` Federico Vaga
2019-09-02 18:10 ` Ingo Molnar
2019-09-02 19:19 ` Federico Vaga
2019-09-02 20:21 ` Jonathan Corbet [this message]
2019-09-02 21:07 ` Federico Vaga
2019-09-03 2:38 ` Matthew Wilcox
2019-09-05 8:21 ` Federico Vaga
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=20190902142133.37e106af@lwn.net \
--to=corbet@lwn.net \
--cc=federico.vaga@vaga.pv.it \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=will@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.