From: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.de>,
Jaroslav Kysela <perex@perex.cz>
Subject: Re: [PATCH] ALSA: aaci: report FIFO size in frames
Date: Tue, 2 Apr 2024 01:01:24 +0200 [thread overview]
Message-ID: <Zgs8xAB3a6zWc0w6@ugly> (raw)
In-Reply-To: <ZgsgHiFbbmjuD+tT@shell.armlinux.org.uk>
On Mon, Apr 01, 2024 at 09:59:10PM +0100, Russell King (Oracle) wrote:
>On Mon, Apr 01, 2024 at 04:17:53PM +0200, Oswald Buddenhagen wrote:
>> i think that speculative/rfc patches are a perfectly fine way to get
>> things clarified, and the linux kernel is no exception to that.
>
>This wasn't a "speculative/rfc" patch. Such patches get marked with
>"RFC" in the tag.
>
putting an obvious disclaimer/question section after a three-dash line
is a perfectly sufficient way to mark such a patch. at least if the
receiver is actually interested in cooperation rather than harping on
formalities.
>> > Comments are not always correct.
>> >
>> so how about taking the opportunity to fix this one?
>
>I don't think this comment is incorrect.
>
>"ALSA wants the byte-size of the FIFOs."
>
>That is a fact when the flag you refer to is not set.
>
yet the formulation also suggests that this is something that just is,
rather than something that the code has control over.
>[...]
>At some point, knowledge has to be assumed.
>
the problem is the omission of specific information that is in this
context at least as pertinent as the information that _was_ supplied.
the code is also somewhat special in that it implements an interface,
which makes it more likely to be "visited" by outsiders than some
implementation details. it makes sense to take that into account in
related comments.
next prev parent reply other threads:[~2024-04-01 23:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 10:13 [PATCH] ALSA: aaci: report FIFO size in frames Oswald Buddenhagen
2024-04-01 10:31 ` Russell King (Oracle)
2024-04-01 10:37 ` Russell King (Oracle)
2024-04-01 10:53 ` Oswald Buddenhagen
2024-04-01 11:04 ` Russell King (Oracle)
2024-04-01 11:45 ` Oswald Buddenhagen
2024-04-01 13:34 ` Russell King (Oracle)
2024-04-01 14:17 ` Oswald Buddenhagen
2024-04-01 20:59 ` Russell King (Oracle)
2024-04-01 23:01 ` Oswald Buddenhagen [this message]
2024-04-01 23:25 ` Russell King (Oracle)
2024-04-02 10:46 ` Oswald Buddenhagen
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=Zgs8xAB3a6zWc0w6@ugly \
--to=oswald.buddenhagen@gmx.de \
--cc=alsa-devel@alsa-project.org \
--cc=linux@armlinux.org.uk \
--cc=perex@perex.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox