From: kbuild test robot <lkp@intel.com> To: Andreas Gruenbacher <agruenba@redhat.com> Cc: kbuild-all@01.org, cluster-devel@redhat.com, "Christoph Hellwig" <hch@lst.de>, "Bob Peterson" <rpeterso@redhat.com>, "Jan Kara" <jack@suse.cz>, "Dave Chinner" <david@fromorbit.com>, "Ross Lagerwall" <ross.lagerwall@citrix.com>, "Mark Syms" <Mark.Syms@citrix.com>, "Edwin Török" <edvin.torok@citrix.com>, linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, "Andreas Gruenbacher" <agruenba@redhat.com> Subject: [RFC PATCH] gfs2: gfs2_iomap_page_ops can be static Date: Fri, 26 Apr 2019 05:01:20 +0800 [thread overview] Message-ID: <20190425210120.GA165926@ivb43> (raw) In-Reply-To: <20190425160913.1878-2-agruenba@redhat.com> Fixes: 9167204805d5 ("gfs2: Fix iomap write page reclaim deadlock") Signed-off-by: kbuild test robot <lkp@intel.com> --- bmap.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/gfs2/bmap.c b/fs/gfs2/bmap.c index 2fae3f4..27c82f4 100644 --- a/fs/gfs2/bmap.c +++ b/fs/gfs2/bmap.c @@ -1011,7 +1011,7 @@ static void gfs2_iomap_page_done(struct inode *inode, loff_t pos, gfs2_trans_end(sdp); } -const struct iomap_page_ops gfs2_iomap_page_ops = { +static const struct iomap_page_ops gfs2_iomap_page_ops = { .page_prepare = gfs2_iomap_page_prepare, .page_done = gfs2_iomap_page_done, };
WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com> To: cluster-devel.redhat.com Subject: [Cluster-devel] [RFC PATCH] gfs2: gfs2_iomap_page_ops can be static Date: Fri, 26 Apr 2019 05:01:20 +0800 [thread overview] Message-ID: <20190425210120.GA165926@ivb43> (raw) In-Reply-To: <20190425160913.1878-2-agruenba@redhat.com> Fixes: 9167204805d5 ("gfs2: Fix iomap write page reclaim deadlock") Signed-off-by: kbuild test robot <lkp@intel.com> --- bmap.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/gfs2/bmap.c b/fs/gfs2/bmap.c index 2fae3f4..27c82f4 100644 --- a/fs/gfs2/bmap.c +++ b/fs/gfs2/bmap.c @@ -1011,7 +1011,7 @@ static void gfs2_iomap_page_done(struct inode *inode, loff_t pos, gfs2_trans_end(sdp); } -const struct iomap_page_ops gfs2_iomap_page_ops = { +static const struct iomap_page_ops gfs2_iomap_page_ops = { .page_prepare = gfs2_iomap_page_prepare, .page_done = gfs2_iomap_page_done, };
next prev parent reply other threads:[~2019-04-25 21:01 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-04-25 16:09 [PATCH v3 1/2] iomap: Add a page_prepare callback Andreas Gruenbacher 2019-04-25 16:09 ` [Cluster-devel] " Andreas Gruenbacher 2019-04-25 16:09 ` [PATCH v3 2/2] gfs2: Fix iomap write page reclaim deadlock Andreas Gruenbacher 2019-04-25 16:09 ` [Cluster-devel] " Andreas Gruenbacher 2019-04-25 21:01 ` kbuild test robot 2019-04-25 21:01 ` [Cluster-devel] " kbuild test robot 2019-04-25 21:01 ` kbuild test robot [this message] 2019-04-25 21:01 ` [Cluster-devel] [RFC PATCH] gfs2: gfs2_iomap_page_ops can be static kbuild test robot 2019-04-25 19:09 ` [PATCH v3 1/2] iomap: Add a page_prepare callback kbuild test robot 2019-04-25 19:09 ` [Cluster-devel] " kbuild test robot 2019-04-26 8:30 ` Jan Kara 2019-04-26 8:30 ` [Cluster-devel] " Jan Kara 2019-04-26 13:11 ` Andreas Gruenbacher 2019-04-26 13:11 ` [Cluster-devel] " Andreas Gruenbacher
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=20190425210120.GA165926@ivb43 \ --to=lkp@intel.com \ --cc=Mark.Syms@citrix.com \ --cc=agruenba@redhat.com \ --cc=cluster-devel@redhat.com \ --cc=david@fromorbit.com \ --cc=edvin.torok@citrix.com \ --cc=hch@lst.de \ --cc=jack@suse.cz \ --cc=kbuild-all@01.org \ --cc=linux-fsdevel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=ross.lagerwall@citrix.com \ --cc=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: linkBe 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.