From: Dimitri Sivanich <sivanich@hpe.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Russ Anderson <rja@hpe.com>, Mike Travis <mike.travis@hpe.com>,
Jason Gunthorpe <jgg@mellanox.com>,
Bharath Vedartham <linux.bhar@gmail.com>,
linux-kernel@vger.kernel.org, Dimitri Sivanich <sivanich@hpe.com>
Subject: Re: status of drivers/misc/sgi-gru?
Date: Mon, 12 Aug 2019 07:56:25 -0500 [thread overview]
Message-ID: <20190812125625.GA27091@hpe.com> (raw)
In-Reply-To: <20190812080518.GA29629@infradead.org>
Yes, the GRU driver is still maintained, and I have been in contact with Bharath
about my pending testing of his changes.
On Mon, Aug 12, 2019 at 01:05:19AM -0700, Christoph Hellwig wrote:
> Hi dear ex-SGI folks,
>
> do you know if the GRU driver is still maintained and in use?
>
> Both Bharath and Jason have been posting changes to it that need
> review, and I've just been discussing even more extensive mmu_notifier
> changes with Jason that will require some very careful review. If the
> driver is still need I'd really like to hear your feedback.
prev parent reply other threads:[~2019-08-12 12:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 8:05 status of drivers/misc/sgi-gru? Christoph Hellwig
2019-08-12 12:56 ` Dimitri Sivanich [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=20190812125625.GA27091@hpe.com \
--to=sivanich@hpe.com \
--cc=hch@infradead.org \
--cc=jgg@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.bhar@gmail.com \
--cc=mike.travis@hpe.com \
--cc=rja@hpe.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