From: Sachin Sant <sachinp@linux.vnet.ibm.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-block@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
linux-next@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [linux-next] Read-only file system after boot (powerpc)
Date: Mon, 29 Nov 2021 15:56:23 +0530 [thread overview]
Message-ID: <2CD932C2-A553-4676-B73C-5A65198F73F2@linux.vnet.ibm.com> (raw)
In-Reply-To: <20211129095947.GA32642@lst.de>
> On 29-Nov-2021, at 3:29 PM, Christoph Hellwig <hch@lst.de> wrote:
>
> 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?
Thanks. Yes, this patch fixes the problem for me.
-Sachin
prev parent reply other threads:[~2021-11-29 10:27 UTC|newest]
Thread overview: 3+ 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 9:59 ` Christoph Hellwig
2021-11-29 10:26 ` Sachin Sant [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=2CD932C2-A553-4676-B73C-5A65198F73F2@linux.vnet.ibm.com \
--to=sachinp@linux.vnet.ibm.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
/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