Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
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: Mon, 1 Apr 2024 16:17:53 +0200	[thread overview]
Message-ID: <ZgrCEU6rHuEtT6/8@ugly> (raw)
In-Reply-To: <Zgq33GqYqtln0qyX@shell.armlinux.org.uk>

On Mon, Apr 01, 2024 at 02:34:20PM +0100, Russell King (Oracle) wrote:
>Oh FFS. So you generated a patch based on the contents of a mere
>comment? That is NOT how kernel development should be done. Do not do
>this.
>
i think that speculative/rfc patches are a perfectly fine way to get
things clarified, and the linux kernel is no exception to that.

>Comments are not always correct.
>
so how about taking the opportunity to fix this one?

>NAK to *all* your patches whether I've seen them or
>not if this is how you behave.
>
it was a pleasure to work with you.


  reply	other threads:[~2024-04-01 14:18 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 [this message]
2024-04-01 20:59               ` Russell King (Oracle)
2024-04-01 23:01                 ` Oswald Buddenhagen
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=ZgrCEU6rHuEtT6/8@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