ocfs2-devel.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: change slot number type s16 to u16
Date: Mon, 3 Aug 2020 17:45:54 -0700	[thread overview]
Message-ID: <20200803174554.32619bbe8a5222c661d58d28@linux-foundation.org> (raw)
In-Reply-To: <d1d2686d-6aa1-d241-73cd-c438e23183a2@suse.com>

On Mon, 3 Aug 2020 14:43:23 +0800 Gang He <ghe@suse.com> wrote:

> Could you help to commit this patch to Linus git tree? since this patch 
> will fix the latest patch (ocfs2: fix value of OCFS2_INVALID_SLOT).
> So far, the current ocfs2 code under Linus git tree does NOT work.

It's in the queue for 5.9-rc1, with a cc:stable.

      reply	other threads:[~2020-08-04  0:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-27  0:12 [Ocfs2-devel] [PATCH] ocfs2: change slot number type s16 to u16 Junxiao Bi
2020-06-29  1:47 ` Joseph Qi
2020-07-03  8:45 ` Gang He
2020-07-03 12:11   ` Joseph Qi
2020-08-03  6:43     ` Gang He
2020-08-04  0:45       ` Andrew Morton [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=20200803174554.32619bbe8a5222c661d58d28@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=ocfs2-devel@oss.oracle.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).