From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A8B29CA9EC0 for ; Mon, 28 Oct 2019 14:44:22 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 817C921744 for ; Mon, 28 Oct 2019 14:44:22 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2390286AbfJ1OoV (ORCPT ); Mon, 28 Oct 2019 10:44:21 -0400 Received: from mx2.suse.de ([195.135.220.15]:59076 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727982AbfJ1OoV (ORCPT ); Mon, 28 Oct 2019 10:44:21 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 3C01CAC2D; Mon, 28 Oct 2019 14:44:19 +0000 (UTC) Date: Mon, 28 Oct 2019 15:44:19 +0100 Message-ID: From: Takashi Iwai To: Markus Elfring Cc: Navid Emamdoost , alsa-devel@alsa-project.org, linux-doc@vger.kernel.org, Navid Emamdoost , Kangjie Lu , Stephen McCamant , Greg Kroah-Hartman , Richard Fontana , Thomas Gleixner , kernel-janitors@vger.kernel.org, LKML Subject: Re: [alsa-devel] ALSA: korg1212: Checking exception handling in snd_korg1212_create() In-Reply-To: <0daa3e27-3d1f-3040-f8e7-92ce91a97687@web.de> References: <0daa3e27-3d1f-3040-f8e7-92ce91a97687@web.de> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 28 Oct 2019 15:40:09 +0100, Markus Elfring wrote: > > >> Can the properties of this programming interface be documented also together > >> with the function declaration for the safer handling of ALSA components? > >> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/sound/kernel-api/writing-an-alsa-driver.rst?id=d6d5df1db6e9d7f8f76d2911707f7d5877251b02#n567 > > > > I can think of only adding some comment at each point mentioning that > > the resource will be managed by the device destructor. > > * Which places will be corresponding update candidates? At each place where this kind of code is seen. > * Would you like to choose the wording? I myself don't mind as long as it's clearly understandable for human being. > >> Can any more API information help to improve automatic source code analysis > >> around similar functions? > > > > If anything we can add, let me know. > > Will any tags become more helpful also for the software documentation? It's my question. thanks, Takashi From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Date: Mon, 28 Oct 2019 14:44:19 +0000 Subject: Re: [alsa-devel] ALSA: korg1212: Checking exception handling in snd_korg1212_create() Message-Id: List-Id: References: <0daa3e27-3d1f-3040-f8e7-92ce91a97687@web.de> In-Reply-To: <0daa3e27-3d1f-3040-f8e7-92ce91a97687@web.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: Markus Elfring Cc: alsa-devel@alsa-project.org, linux-doc@vger.kernel.org, kernel-janitors@vger.kernel.org, Greg Kroah-Hartman , Kangjie Lu , LKML , Richard Fontana , Navid Emamdoost , Stephen McCamant , Thomas Gleixner , Navid Emamdoost On Mon, 28 Oct 2019 15:40:09 +0100, Markus Elfring wrote: >=20 > >> Can the properties of this programming interface be documented also to= gether > >> with the function declaration for the safer handling of ALSA component= s? > >> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tre= e/Documentation/sound/kernel-api/writing-an-alsa-driver.rst?id=D6d5df1db6e9= d7f8f76d2911707f7d5877251b02#n567 > > > > I can think of only adding some comment at each point mentioning that > > the resource will be managed by the device destructor. >=20 > * Which places will be corresponding update candidates? At each place where this kind of code is seen. > * Would you like to choose the wording? I myself don't mind as long as it's clearly understandable for human being. > >> Can any more API information help to improve automatic source code ana= lysis > >> around similar functions? > > > > If anything we can add, let me know. >=20 > Will any tags become more helpful also for the software documentation? It's my question. thanks, Takashi From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.7 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 65189CA9EC0 for ; Mon, 28 Oct 2019 14:45:22 +0000 (UTC) Received: from alsa0.perex.cz (alsa0.perex.cz [77.48.224.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id D7B5A21783 for ; Mon, 28 Oct 2019 14:45:21 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alsa-project.org header.i=@alsa-project.org header.b="GuC0borb" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org D7B5A21783 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=suse.de Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=alsa-devel-bounces@alsa-project.org Received: from alsa1.perex.cz (alsa1.perex.cz [207.180.221.201]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa0.perex.cz (Postfix) with ESMTPS id F32891F5A; Mon, 28 Oct 2019 15:44:29 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz F32891F5A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1572273920; bh=4/n0DB6czWyxZKG+UFZ0aFviJtjoPa1cL40ulhwz9c4=; h=Date:From:To:In-Reply-To:References:Cc:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=GuC0borby4RP20fxRCm1IH/gPPoA+ezNxCAj/esB5/SpfGW+KhXshvzHUzlFiC85e pyrqyvW0gSj2SA7LNJMi1BueW5j1EMGXrpgsG41H1QbAAiovb3eRzXg1484G9wnFoL hnz29VyDME/756iSwIuX8kUz+Xll80C8j9m6U4Nc= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id 98E98F800E7; Mon, 28 Oct 2019 15:44:29 +0100 (CET) Received: by alsa1.perex.cz (Postfix, from userid 50401) id 5BC9AF80361; Mon, 28 Oct 2019 15:44:22 +0100 (CET) Received: from mx1.suse.de (mx2.suse.de [195.135.220.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa1.perex.cz (Postfix) with ESMTPS id 3A453F80145 for ; Mon, 28 Oct 2019 15:44:19 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz 3A453F80145 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 3C01CAC2D; Mon, 28 Oct 2019 14:44:19 +0000 (UTC) Date: Mon, 28 Oct 2019 15:44:19 +0100 Message-ID: From: Takashi Iwai To: Markus Elfring In-Reply-To: <0daa3e27-3d1f-3040-f8e7-92ce91a97687@web.de> References: <0daa3e27-3d1f-3040-f8e7-92ce91a97687@web.de> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Cc: alsa-devel@alsa-project.org, linux-doc@vger.kernel.org, kernel-janitors@vger.kernel.org, Greg Kroah-Hartman , Kangjie Lu , LKML , Richard Fontana , Navid Emamdoost , Stephen McCamant , Thomas Gleixner , Navid Emamdoost Subject: Re: [alsa-devel] ALSA: korg1212: Checking exception handling in snd_korg1212_create() X-BeenThere: alsa-devel@alsa-project.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Alsa-devel mailing list for ALSA developers - http://www.alsa-project.org" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: alsa-devel-bounces@alsa-project.org Sender: "Alsa-devel" On Mon, 28 Oct 2019 15:40:09 +0100, Markus Elfring wrote: > > >> Can the properties of this programming interface be documented also together > >> with the function declaration for the safer handling of ALSA components? > >> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/sound/kernel-api/writing-an-alsa-driver.rst?id=d6d5df1db6e9d7f8f76d2911707f7d5877251b02#n567 > > > > I can think of only adding some comment at each point mentioning that > > the resource will be managed by the device destructor. > > * Which places will be corresponding update candidates? At each place where this kind of code is seen. > * Would you like to choose the wording? I myself don't mind as long as it's clearly understandable for human being. > >> Can any more API information help to improve automatic source code analysis > >> around similar functions? > > > > If anything we can add, let me know. > > Will any tags become more helpful also for the software documentation? It's my question. thanks, Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org https://mailman.alsa-project.org/mailman/listinfo/alsa-devel