public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Boaz Harrosh <ooo@electrozaur.com>, Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org, osd-dev@open-osd.org
Subject: state of the osdblk driver?
Date: Tue, 21 Oct 2014 05:06:53 -0700	[thread overview]
Message-ID: <20141021120653.GA9530@infradead.org> (raw)

The osdblk driver hsa seen literally no change except for global
API changes since it was merged, and I've never heard of a user.

Is this something we want to keep around?  I just noticed it because
it's the only non-SCSI user of some of the old block layer tagging
functions.

             reply	other threads:[~2014-10-21 12:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-21 12:06 Christoph Hellwig [this message]
2014-10-21 12:21 ` state of the osdblk driver? Jeff Garzik
2014-10-21 12:47   ` Boaz Harrosh
2014-10-21 12:56     ` Jeff Garzik
2014-10-21 13:01     ` Christoph Hellwig
2014-10-21 13:24       ` Boaz Harrosh

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=20141021120653.GA9530@infradead.org \
    --to=hch@infradead.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ooo@electrozaur.com \
    --cc=osd-dev@open-osd.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