From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH] gfs2: use inode_lock/unlock instead of accessing i_mutex directly
Date: Mon, 2 May 2016 08:20:46 -0400 (EDT) [thread overview]
Message-ID: <1668446490.60353940.1462191645986.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1462164283-22082-1-git-send-email-adas@redhat.com>
----- Original Message -----
> i_mutex has been replaced by i_rwsem and directly accessing the
> non-existent i_mutex breaks the kernel build.
>
> Signed-off-by: Abhi Das <adas@redhat.com>
> CC: Stephen Rothwell <sfr@canb.auug.org.au>
> CC: Al Viro <viro@ZenIV.linux.org.uk>
> ---
Hi Abhi,
Thanks. This is now applied to the for-next branch of the linux-gfs2 tree:
https://git.kernel.org/cgit/linux/kernel/git/gfs2/linux-gfs2.git/commit/fs/gfs2?h=for-next&id=80f4781d2c0ba63bf9ab4de90a6829a1368b80a3
Regards,
Bob Peterson
Red Hat File Systems
prev parent reply other threads:[~2016-05-02 12:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 4:44 [Cluster-devel] [GFS2 PATCH] gfs2: use inode_lock/unlock instead of accessing i_mutex directly Abhi Das
2016-05-02 12:20 ` Bob Peterson [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=1668446490.60353940.1462191645986.JavaMail.zimbra@redhat.com \
--to=rpeterso@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).