From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bob Peterson Date: Mon, 29 Jan 2018 08:30:36 -0500 (EST) Subject: [Cluster-devel] [PATCH v2 0/3] gfs2: Add new resource group header fields In-Reply-To: <26edf85c-390c-8b10-0274-85ba2779c860@redhat.com> References: <20171208145942.17717-1-anprice@redhat.com> <33817411.39938367.1512746043539.JavaMail.zimbra@redhat.com> <26edf85c-390c-8b10-0274-85ba2779c860@redhat.com> Message-ID: <881011464.4642526.1517232636641.JavaMail.zimbra@redhat.com> List-Id: To: cluster-devel.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi Andy, ----- Original Message ----- | I've just realised that these aren't in for-next despite the positive | response. Can they get in for the upcoming merge window? Your three patches are indeed already included in for-next and have been for some time. I'm not sure why you're not seeing them, but I needed to do several push --force operations to fix various patch reworks, screw-ups, and dependencies. Perhaps you just need to git pull again? Below are links to the patches in for-next: | Andrew Price (3): | gfs2: Add a next-resource-group pointer to resource groups https://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git/commit/fs/gfs2?h=for-next&id=65adc27375a85beb57c3869cedb2a410fad9c288 | gfs2: Add rindex fields to rgrp headers https://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git/commit/fs/gfs2?h=for-next&id=166725d96322473305e35f9d580591a01697ab29 | gfs2: Add a crc field to resource group headers https://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git/commit/fs/gfs2?h=for-next&id=850d2d915fa69011bef9bd668499cce889fdd8b3 So yes, they should go into the next merge window. Regards, Bob Peterson Red Hat File Systems