From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sasha Levin Date: Sat, 29 Aug 2020 21:59:25 +0000 Subject: [Cluster-devel] [PATCH] gfs2: Make sure we don't miss any delayed withdraws In-Reply-To: <20200829092656.1173430-1-agruenba@redhat.com> References: <20200829092656.1173430-1-agruenba@redhat.com> Message-ID: <20200829215926.234BF208CA@mail.kernel.org> List-Id: To: cluster-devel.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi [This is an automated email] This commit has been processed because it contains a "Fixes:" tag fixing commit: ca399c96e96e ("gfs2: flesh out delayed withdraw for gfs2_log_flush"). The bot has tested the following trees: v5.8.5. v5.8.5: Failed to apply! Possible dependencies: 462582b99b60 ("gfs2: add some much needed cleanup for log flushes that fail") NOTE: The patch will not be queued to stable trees until it is upstream. How should we proceed with this patch? -- Thanks Sasha