From: Christoph Hellwig <hch@lst.de>
To: Sachin Sant <sachinp@linux.vnet.ibm.com>
Cc: linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
linux-next@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
Jens Axboe <axboe@kernel.dk>
Subject: Re: [linux-next] Read-only file system after boot (powerpc)
Date: Mon, 29 Nov 2021 10:59:47 +0100 [thread overview]
Message-ID: <20211129095947.GA32642@lst.de> (raw)
In-Reply-To: <87F94FF1-5D9D-475B-B083-C101DDB7A108@linux.vnet.ibm.com>
Can you check if your tree already includes this commit:
https://git.kernel.dk/cgit/linux-block/commit/?h=for-5.17/block&id=3f39d47d7ad858c024bd777f5f2a86fa7f6a9f14
and if not see if that fixes the problem?
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Sachin Sant <sachinp@linux.vnet.ibm.com>
Cc: linux-block@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
linux-next@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
Christoph Hellwig <hch@lst.de>
Subject: Re: [linux-next] Read-only file system after boot (powerpc)
Date: Mon, 29 Nov 2021 10:59:47 +0100 [thread overview]
Message-ID: <20211129095947.GA32642@lst.de> (raw)
In-Reply-To: <87F94FF1-5D9D-475B-B083-C101DDB7A108@linux.vnet.ibm.com>
Can you check if your tree already includes this commit:
https://git.kernel.dk/cgit/linux-block/commit/?h=for-5.17/block&id=3f39d47d7ad858c024bd777f5f2a86fa7f6a9f14
and if not see if that fixes the problem?
next prev parent reply other threads:[~2021-11-29 10:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 6:59 [linux-next] Read-only file system after boot (powerpc) Sachin Sant
2021-11-29 6:59 ` Sachin Sant
2021-11-29 9:59 ` Christoph Hellwig [this message]
2021-11-29 9:59 ` Christoph Hellwig
2021-11-29 10:26 ` Sachin Sant
2021-11-29 10:26 ` Sachin Sant
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=20211129095947.GA32642@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sachinp@linux.vnet.ibm.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 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.