From: David Howells <dhowells@redhat.com>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: dhowells@redhat.com, Al Viro <viro@zeniv.linux.org.uk>,
Maxime Bizon <mbizon@freebox.fr>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] cramfs: fix usage on non-MTD device
Date: Mon, 21 Oct 2019 14:45:39 +0100 [thread overview]
Message-ID: <18923.1571665539@warthog.procyon.org.uk> (raw)
In-Reply-To: <nycvar.YSQ.7.76.1910191518180.1546@knanqh.ubzr>
Nicolas Pitre <nico@fluxnic.net> wrote:
> From: Maxime Bizon <mbizon@freebox.fr>
>
> When both CONFIG_CRAMFS_MTD and CONFIG_CRAMFS_BLOCKDEV are enabled, if
> we fail to mount on MTD, we don't try on block device.
>
> Fixes: 74f78fc5ef43 ("vfs: Convert cramfs to use the new mount API")
>
> Signed-off-by: Maxime Bizon <mbizon@freebox.fr>
> Signed-off-by: Nicolas Pitre <nico@fluxnic.net>
Acked-by: David Howells <dhowells@redhat.com>
next prev parent reply other threads:[~2019-10-21 13:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-19 19:24 [PATCH] cramfs: fix usage on non-MTD device Nicolas Pitre
2019-10-21 13:45 ` David Howells [this message]
2019-10-21 14:04 ` Al Viro
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=18923.1571665539@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mbizon@freebox.fr \
--cc=nico@fluxnic.net \
--cc=viro@zeniv.linux.org.uk \
/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).