From: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
To: alsa-devel@alsa-project.org
Subject: Re: [PATCH] ALSA: document that struct __snd_pcm_mmap_control64 is messed up
Date: Thu, 6 Apr 2023 08:46:51 +0200 [thread overview]
Message-ID: <ZC5q2zwCmhaTE6ba@ugly> (raw)
In-Reply-To: <87355dwnr8.wl-tiwai@suse.de>
On Thu, Apr 06, 2023 at 08:03:39AM +0200, Takashi Iwai wrote:
>On Wed, 05 Apr 2023 22:12:19 +0200,
>Oswald Buddenhagen wrote:
>>
>> I suppose this can't be changed anymore due to binary compat concerns.
>
>Yes, please check the thread at
> https://lore.kernel.org/all/29QBMJU8DE71E.2YZSH8IHT5HMH@mforney.org/
>
>> + __pad_before_uframe __pad2; // BUG: this should have been __pad_after_uframe!
>
>Writing this alone doesn't help much. Actual help would be to mention
>that this typo is kept intentionally.
>
hmm, my thinking is that the immediate response to reading that comment
would be "so why don't you change it?!", at which point the person would
either realize by themselves that this is subject to binary compat
constraints, or would git-blame it and see the explanation.
anyway, my concern is keeping this *short*, so it doesn't distract.
maybe
// BUG: should be __pad_after_uframe, but binary compat
would do, though obviously the grammar kinda sucks.
the (too) long version could be
// BUG: this should be __pad_after_uframe, but
// binary compatibility constraints prevent a fix.
choose your death, i'll deliver it. ;-)
next prev parent reply other threads:[~2023-04-06 6:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 20:12 [PATCH] ALSA: document that struct __snd_pcm_mmap_control64 is messed up Oswald Buddenhagen
2023-04-06 6:03 ` Takashi Iwai
2023-04-06 6:46 ` Oswald Buddenhagen [this message]
2023-04-06 7:48 ` Takashi Iwai
2023-04-06 11:15 ` [PATCH v2] " Oswald Buddenhagen
2023-04-06 12:29 ` Takashi Iwai
2023-04-06 12:34 ` Oswald Buddenhagen
2023-04-06 13:23 ` 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=ZC5q2zwCmhaTE6ba@ugly \
--to=oswald.buddenhagen@gmx.de \
--cc=alsa-devel@alsa-project.org \
/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.