From: Markus Elfring <Markus.Elfring@web.de>
To: Takashi Iwai <tiwai@suse.de>, Navid Emamdoost <emamd001@umn.edu>,
alsa-devel@alsa-project.org, linux-doc@vger.kernel.org
Cc: Navid Emamdoost <navid.emamdoost@gmail.com>,
Kangjie Lu <kjlu@umn.edu>, Stephen McCamant <smccaman@umn.edu>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Richard Fontana <rfontana@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
kernel-janitors@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [alsa-devel] ALSA: korg1212: Checking exception handling in snd_korg1212_create()
Date: Mon, 28 Oct 2019 15:40:09 +0100 [thread overview]
Message-ID: <0daa3e27-3d1f-3040-f8e7-92ce91a97687@web.de> (raw)
In-Reply-To: <s5ho8y1au4h.wl-tiwai@suse.de>
>> 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?
* Would you like to choose the wording?
>> 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?
Regards,
Markus
WARNING: multiple messages have this Message-ID (diff)
From: Markus Elfring <Markus.Elfring@web.de>
To: Takashi Iwai <tiwai@suse.de>, Navid Emamdoost <emamd001@umn.edu>,
alsa-devel@alsa-project.org, linux-doc@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kangjie Lu <kjlu@umn.edu>, LKML <linux-kernel@vger.kernel.org>,
Richard Fontana <rfontana@redhat.com>,
Stephen McCamant <smccaman@umn.edu>,
Thomas Gleixner <tglx@linutronix.de>,
Navid Emamdoost <navid.emamdoost@gmail.com>
Subject: Re: [alsa-devel] ALSA: korg1212: Checking exception handling in snd_korg1212_create()
Date: Mon, 28 Oct 2019 14:40:09 +0000 [thread overview]
Message-ID: <0daa3e27-3d1f-3040-f8e7-92ce91a97687@web.de> (raw)
In-Reply-To: <s5ho8y1au4h.wl-tiwai@suse.de>
>> 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?
* Would you like to choose the wording?
>> 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?
Regards,
Markus
WARNING: multiple messages have this Message-ID (diff)
From: Markus Elfring <Markus.Elfring@web.de>
To: Takashi Iwai <tiwai@suse.de>, Navid Emamdoost <emamd001@umn.edu>,
alsa-devel@alsa-project.org, linux-doc@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kangjie Lu <kjlu@umn.edu>, LKML <linux-kernel@vger.kernel.org>,
Richard Fontana <rfontana@redhat.com>,
Stephen McCamant <smccaman@umn.edu>,
Thomas Gleixner <tglx@linutronix.de>,
Navid Emamdoost <navid.emamdoost@gmail.com>
Subject: Re: [alsa-devel] ALSA: korg1212: Checking exception handling in snd_korg1212_create()
Date: Mon, 28 Oct 2019 15:40:09 +0100 [thread overview]
Message-ID: <0daa3e27-3d1f-3040-f8e7-92ce91a97687@web.de> (raw)
In-Reply-To: <s5ho8y1au4h.wl-tiwai@suse.de>
>> 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?
* Would you like to choose the wording?
>> 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?
Regards,
Markus
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-10-28 14:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-27 19:12 [PATCH] ALSA: pci: Fix memory leak in snd_korg1212_create Navid Emamdoost
2019-10-27 19:12 ` [alsa-devel] " Navid Emamdoost
2019-10-27 20:40 ` Markus Elfring
2019-10-27 20:40 ` [alsa-devel] " Markus Elfring
2019-10-27 20:40 ` Markus Elfring
2019-10-28 8:19 ` Markus Elfring
2019-10-28 8:19 ` [alsa-devel] " Markus Elfring
2019-10-28 8:19 ` Markus Elfring
2019-10-28 6:31 ` [PATCH] " Takashi Iwai
2019-10-28 6:31 ` [alsa-devel] " Takashi Iwai
2019-10-28 9:00 ` [alsa-devel] ALSA: korg1212: Checking exception handling in snd_korg1212_create() Markus Elfring
2019-10-28 9:00 ` Markus Elfring
2019-10-28 9:00 ` Markus Elfring
2019-10-28 13:15 ` Takashi Iwai
2019-10-28 13:15 ` Takashi Iwai
2019-10-28 13:15 ` Takashi Iwai
2019-10-28 14:40 ` Markus Elfring [this message]
2019-10-28 14:40 ` Markus Elfring
2019-10-28 14:40 ` Markus Elfring
2019-10-28 14:44 ` Takashi Iwai
2019-10-28 14:44 ` Takashi Iwai
2019-10-28 14:44 ` Takashi Iwai
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=0daa3e27-3d1f-3040-f8e7-92ce91a97687@web.de \
--to=markus.elfring@web.de \
--cc=alsa-devel@alsa-project.org \
--cc=emamd001@umn.edu \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kjlu@umn.edu \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=navid.emamdoost@gmail.com \
--cc=rfontana@redhat.com \
--cc=smccaman@umn.edu \
--cc=tglx@linutronix.de \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.