From: Finn Thain <fthain@telegraphics.com.au>
To: Boaz Harrosh <ooo@electrozaur.com>
Cc: Bart Van Assche <bvanassche@acm.org>,
Christoph Hellwig <hch@lst.de>,
martin.petersen@oracle.com,
Nick Desaulniers <ndesaulniers@google.com>,
Nathan Chancellor <natechancellor@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
osd-dev@open-osd.org, linux-scsi@vger.kernel.org,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: remove exofs and the T10 OSD code V2
Date: Thu, 1 Nov 2018 09:07:51 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LNX.2.21.1811010846490.8@nippy.intranet> (raw)
In-Reply-To: <6794b3a0-fe57-cd8b-3ad3-3a590121b12a@electrozaur.com>
On Wed, 31 Oct 2018, Boaz Harrosh wrote:
> > [...] All changes made by other kernel developers than you are the
> > result of tree-wide refactoring, compiler warning fixes, fixes for
> > issues detected by static source code analyzers or spelling fixes.
> > Hence my question: how big is the user base of the exofs and osd
> > kernel drivers?
> >
>
> Not big at all. And none of them production setups. As I said mainly
> used by academia.
>
For its part, academia has provided tools to automate the mindless and
error-prone refactoring which Bart points to. I'm mainly thinking of LLVM
and Ocaml. (I'm not a computer scientist.)
But I fear that code transformation tools lie beyond the skill and ability
of those of us who submit spelling fixes.
So the tools need to be made more usable in this setting. Corporate users
of kernel code who happen to have their own IDE products (Microsoft,
Google, etc.) have an opportunity here.
--
> Thanks
> Boaz
>
> > Thanks,
> > Bart.
>
>
prev parent reply other threads:[~2018-10-31 22:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-27 8:20 remove exofs and the T10 OSD code V2 Christoph Hellwig
2018-10-27 8:20 ` [PATCH 1/2] fs: remove exofs Christoph Hellwig
2018-10-29 20:41 ` Bart Van Assche
2018-10-27 8:20 ` [PATCH 2/2] scsi: remove the SCSI OSD library Christoph Hellwig
2018-10-29 20:43 ` Bart Van Assche
2018-10-27 20:32 ` remove exofs and the T10 OSD code V2 Nick Desaulniers
2018-10-29 20:42 ` Jens Axboe
2018-10-30 7:45 ` Christoph Hellwig
2018-10-31 15:57 ` Boaz Harrosh
2018-10-31 21:10 ` Douglas Gilbert
2018-11-01 0:03 ` Boaz Harrosh
2018-11-01 11:13 ` Douglas Gilbert
2018-10-31 15:59 ` Jens Axboe
2018-10-31 16:34 ` Boaz Harrosh
2018-10-31 17:29 ` Bart Van Assche
2018-10-31 17:47 ` Boaz Harrosh
2018-10-31 22:07 ` Finn Thain [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=alpine.LNX.2.21.1811010846490.8@nippy.intranet \
--to=fthain@telegraphics.com.au \
--cc=bvanassche@acm.org \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=ooo@electrozaur.com \
--cc=osd-dev@open-osd.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).