From: Rik van Riel <riel@redhat.com>
To: Nicholas Mc Guire <der.herr@hofr.at>, Al Viro <viro@zeniv.linux.org.uk>
Cc: John Stultz <john.stultz@linaro.org>,
Ingo Molnar <mingo@kernel.org>,
Stephen Boyd <sboyd@codeaurora.org>,
Trond Myklebust <trond.myklebust@primarydata.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] doc fix - brlock was removed in the 3.13 kernel series
Date: Thu, 25 Dec 2014 09:42:30 -0500 [thread overview]
Message-ID: <549C2256.5010704@redhat.com> (raw)
In-Reply-To: <1419506981-23952-1-git-send-email-der.herr@hofr.at>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12/25/2014 06:29 AM, Nicholas Mc Guire wrote:
> The brlock was completely removed in the 3.13 kernel series. see
> commit 0f6ed63b1707 ("no need to keep brlock macros anymore...")
>
> It seems that documentation in seqlock.h was not updated to
> reflect this. This patch drops the (hopefully last) false brlock
> reference. All remaining references to brlock refer to byte-range
> locks (notably in cifs) and not to "Big Reader Lock" and should be
> correct.
>
> patch is against 3.19.0-rc1 linux-next
>
> Signed-off-by: Nicholas Mc Guire <der.herr@hofr.at>
Reviewed-by: Rik van Riel <riel@redhat.com>
- --
All rights reversed
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJUnCJVAAoJEM553pKExN6DTl4IALfePxNFoRphS8CmLbONtqmi
Bs4gu9ngJq6BLenk6bOF5wfMCRTBXHagWnn14wrjjZOFBkh9Fh+Zy+8GKS31rwUL
GNsCdOUoSBRts2xXMCIxX2cE6+xclYXD5/nWC0InrGtYGfMQmVr5hdLy3UYQu5GO
M0JaWKuvZE06/pz4ntPKWx0wX15o12ojHQy1IgD9d/J5pe2odAZ2WIueioJAqVes
0PM3rgSlsdFanI+RNAm5OUmTNqVF9S+ctbdjJN0MpJVBBun1XtdyefhnBeNRZIRf
9wmMiHU5sFcg3wEraIQ2lZoPCvFcNw4FHt95S5wS3zNI8FJUN0zm4gLe36hh0EU=
=qaLQ
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2014-12-25 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-25 11:29 [PATCH] doc fix - brlock was removed in the 3.13 kernel series Nicholas Mc Guire
2014-12-25 14:42 ` Rik van Riel [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=549C2256.5010704@redhat.com \
--to=riel@redhat.com \
--cc=der.herr@hofr.at \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=trond.myklebust@primarydata.com \
--cc=viro@zeniv.linux.org.uk \
/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