ocfs2-devel.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Junxiao Bi <junxiao.bi@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] missing patch in recent kernels?
Date: Thu, 16 Jul 2020 08:55:48 -0700	[thread overview]
Message-ID: <827a3bc7-fbb7-6b8f-816f-2f8174d11456@oracle.com> (raw)
In-Reply-To: <alpine.LSU.2.21.2007161726340.21202@er-systems.de>

It's in mm and linux-next, i think it will be soon merged by Andrew.

Thanks,

Junxiao.

On 7/16/20 8:32 AM, Thomas Voegtle wrote:
>
> Hello,
>
>
> I see the same Oops on my system as in:
> https://oss.oracle.com/pipermail/ocfs2-devel/2020-July/015232.html
>
> I used v4.9.230 which included (in 4.9.229):
> ocfs2-fix-panic-on-nfs-server-over-ocfs2.patch
> ocfs2-fix-value-of-ocfs2_invalid_slot.patch
> ocfs2-load-global_inode_alloc.patch
>
> Isn't then that patch named "ocfs2: change slot number type s16 to
> u16" missing mentioned in that mail thread?
>
> I even don't find it in the main linux branch?
>
>
> ?? Thomas
>
>
>
>
>

           reply	other threads:[~2020-07-16 15:55 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <alpine.LSU.2.21.2007161726340.21202@er-systems.de>]

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=827a3bc7-fbb7-6b8f-816f-2f8174d11456@oracle.com \
    --to=junxiao.bi@oracle.com \
    --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).