From: Matthew Wilcox <willy@infradead.org>
To: Stuart Swales <stuart.swales.croftnuisk@gmail.com>
Cc: Ben Dooks <ben-linux-arm@fluff.org>,
Russell King - ARM Linux admin <linux@armlinux.org.uk>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: fs/adfs - keep or kill it?
Date: Thu, 4 Apr 2019 13:55:45 -0700 [thread overview]
Message-ID: <20190404205545.GL22763@bombadil.infradead.org> (raw)
In-Reply-To: <0b7bcf91-500b-e25a-4a71-f41f3ca8c292@gmail.com>
On Thu, Apr 04, 2019 at 09:44:24PM +0100, Stuart Swales wrote:
> On 04/04/2019 11:35, Russell King - ARM Linux admin wrote:
> Have posted on the RISC OS Open site. I imagine some people will
> complain just because they can. Can't see a need for it in new kernels
> myself; people can always use old systems if they need to get data off
> old ADFS IDE drives like I had to.
If it's just grabbing old data, it's far better to do that with a
userspace tool which understands the ADFS layout (several exist).
The only good reason for keeping fs/adfs/ alive is if there's need to
continue to access data that lives on an ADFS filesystem and needs to
be read/written by both a RISC OS host and a Linux host.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-04-04 20:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 10:35 fs/adfs - keep or kill it? Russell King - ARM Linux admin
2019-04-04 20:44 ` Stuart Swales
2019-04-04 20:55 ` Matthew Wilcox [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=20190404205545.GL22763@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=ben-linux-arm@fluff.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=stuart.swales.croftnuisk@gmail.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).