From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Wilcox Subject: Re: [RFC PATCH 11/13] mm/vas: Introduce VAS segments - shareable address space regions Date: Mon, 13 Mar 2017 15:27:58 -0700 Message-ID: <20170313222758.GB4033@bombadil.infradead.org> References: <20170313221415.9375-1-till.smejkal@gmail.com> <20170313221415.9375-12-till.smejkal@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=UWdI7wBs7rGouqV0XeDza2pmt4DAKIm1H/lulT3x93k=; b=F0xPQHX7qgIf0Y C2cznFCtpJwUgQnMc6xvnm2ZcTc6OJcL0g5Uw8mYq4sNe2wQJHZWx+naDWlYjlV/+zwjynC+nq8Mm FnvnWSflyGDf+8G5YNmj5l4zKw81ZWh+OdKaja+EsFQEqRegbwZRMb6L7ROW/h2reftSPBLVIdoGv 5bqfoIQRTAi+G66otNekneJZfeNwcXiuXTfXXrIusLYp1/Qv3fp2IDHFvXWu2AhaxfRebNDTcyvjU RFPlnfUQjvqrPTSJw7JjDY18BaCfT+uevX4snWLgCtaMpuIBdnb0TJB6HmH5Yzr2FwLilD3odCiyh fhTMRdjhu1kN7dbfUUew==; Content-Disposition: inline In-Reply-To: <20170313221415.9375-12-till.smejkal@gmail.com> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-mtd" Errors-To: linux-mtd-bounces+gldm-linux-mtd-36=gmane.org@lists.infradead.org To: Till Smejkal Cc: linux-mips@linux-mips.org, linux-s390@vger.kernel.org, Rich Felker , linux-ia64@vger.kernel.org, linux-sh@vger.kernel.org, Peter Zijlstra , Benjamin Herrenschmidt , Heiko Carstens , alsa-devel@alsa-project.org, linux-usb@vger.kernel.org, "James E.J. Bottomley" , "J. Bruce Fields" , Max Filippov , Paul Mackerras , Laurent Pinchart , "H. Peter Anvin" , sparclinux@vger.kernel.org, linux-hexagon@vger.kernel.org, Cyrille Pitchen , Andy Lutomirski , Jeff Layton , linux-kernel@vger.kernel.org, Marek Szyprowski , linux-arch@vger.kernel.org, Boris Brezillon On Mon, Mar 13, 2017 at 03:14:13PM -0700, Till Smejkal wrote: > +/** > + * Create a new VAS segment. > + * > + * @param[in] name: The name of the new VAS segment. > + * @param[in] start: The address where the VAS segment begins. > + * @param[in] end: The address where the VAS segment ends. > + * @param[in] mode: The access rights for the VAS segment. > + * > + * @returns: The VAS segment ID on success, -ERRNO otherwise. > + **/ Please follow the kernel-doc conventions, as described in Documentation/doc-guide/kernel-doc.rst. Also, function documentation goes with the implementation, not the declaration. > +/** > + * Get ID of the VAS segment belonging to a given name. > + * > + * @param[in] name: The name of the VAS segment for which the ID > + * should be returned. > + * > + * @returns: The VAS segment ID on success, -ERRNO > + * otherwise. > + **/ > +extern int vas_seg_find(const char *name); So ... segments have names, and IDs ... and access permissions ... Why isn't this a special purpose filesystem? ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/