From: Christoph Hellwig <hch@lst.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Aditya Garg <gargaditya08@live.com>,
"willy@infradead.org" <willy@infradead.org>,
"ira.weiny@intel.com" <ira.weiny@intel.com>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"bvanassche@acm.org" <bvanassche@acm.org>,
"keescook@chromium.org" <keescook@chromium.org>,
"songmuchun@bytedance.com" <songmuchun@bytedance.com>,
"slava@dubeyko.com" <slava@dubeyko.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] hfsplus: Add module parameter to enable force writes
Date: Sun, 4 Dec 2022 09:07:52 +0100 [thread overview]
Message-ID: <20221204080752.GA26794@lst.de> (raw)
In-Reply-To: <20221202125344.4254ab20d2fe0a8e784b33e8@linux-foundation.org>
NAK. Global module options overriding mount options don't make sense.
If you mount so much write yourself a script, or add the option to the
configuration of the automounting tool of your choice.
next prev parent reply other threads:[~2022-12-04 8:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 6:01 [PATCH] hfsplus: Add module parameter to enable force writes Aditya Garg
2022-12-02 20:38 ` Viacheslav Dubeyko
2022-12-02 20:53 ` Andrew Morton
2022-12-02 21:01 ` Matthew Wilcox
2022-12-02 21:10 ` Andrew Morton
2022-12-03 6:22 ` Aditya Garg
2022-12-04 8:07 ` Christoph Hellwig [this message]
2022-12-04 11:01 ` Aditya Garg
2022-12-06 8:52 ` Christoph Hellwig
2022-12-03 7:11 ` [PATCH v2] " Aditya Garg
2022-12-04 1:05 ` kernel test robot
2022-12-04 6:43 ` Aditya Garg
2022-12-06 15:17 ` Matthew Wilcox
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=20221204080752.GA26794@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=gargaditya08@live.com \
--cc=ira.weiny@intel.com \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=slava@dubeyko.com \
--cc=songmuchun@bytedance.com \
--cc=willy@infradead.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 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.