Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932444AbaJUMVP (ORCPT ); Tue, 21 Oct 2014 08:21:15 -0400 Received: from mail-yh0-f43.google.com ([209.85.213.43]:58275 "EHLO mail-yh0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932125AbaJUMVO (ORCPT ); Tue, 21 Oct 2014 08:21:14 -0400 MIME-Version: 1.0 In-Reply-To: <20141021120653.GA9530@infradead.org> References: <20141021120653.GA9530@infradead.org> Date: Tue, 21 Oct 2014 08:21:13 -0400 Message-ID: Subject: Re: state of the osdblk driver? From: Jeff Garzik To: Christoph Hellwig Cc: Boaz Harrosh , Jeff Garzik , Kernel development list , osd-dev@open-osd.org Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Drop it, if there are no users. It was simulating an OSD, but there did not seem to be much beyond academic interest, and some interest in the use of aforementioned block functions as a useful exercise in block driver writing. On Tue, Oct 21, 2014 at 8:06 AM, Christoph Hellwig wrote: > 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. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/