Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Kuan-Wei Chiu <visitorckw@gmail.com>
To: Ethan Carter Edwards <ethan@ethancedwards.com>
Cc: tiwai@suse.de, tiwai@suse.com, perex@perex.cz, arnd@arndb.de,
	linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
	ryan_richards@creativelabs.com, wychay@ctl.creative.com,
	David Laight <david.laight.linux@gmail.com>
Subject: Re: [PATCH v2] ALSA: ctxfi: Simplify dao_clear_{left,right}_input() functions
Date: Mon, 30 Dec 2024 23:47:09 +0800	[thread overview]
Message-ID: <Z3LAfa0cIY2eboNR@visitorckw-System-Product-Name> (raw)
In-Reply-To: <20241230153243.2874102-1-ethan@ethancedwards.com>

Hi Ethan,

Thank you for your patch. However, there are a few issues:

On Mon, Dec 30, 2024 at 03:32:58PM +0000, Ethan Carter Edwards wrote:
> There was a lote of code duplication in the dao_clear_left_input() and
> dao_clear_right_input() functions. A new function, dao_clear_input(),
> was created and now the left and right functions call it instead of
> repeating themselves.
> 
> Link: https://lore.kernel.org/lkml/NyKCr2VHK_xCQDwNxFKKx2LVd2d_AC2f2j4eAvnD9uRPtb50i2AruCLOp6mHxsGiyYJ0Tgd3Z50Oy1JTi5gPhjd2WQM2skrv7asp3fLl8HU=@ethancedwards.com/
>
Please move the Link: tag to the SoB area without an empty line.

> Signed-off-by: Ethan Carter Edwards <ethan@ethancedwards.com>
> Co-developed-by: David Laight <david.laight.linux@gmail.com>

The Co-developed-by: tag should be immediately followed by the
co-author's Signed-off-by: tag. Additionally, the last Signed-off-by:
tag must always belong to the patch submitter.

See: https://docs.kernel.org/process/submitting-patches.html#when-to-use-acked-by-cc-and-co-developed-by

Regards,
Kuan-Wei

  parent reply	other threads:[~2024-12-30 15:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-30 15:32 [PATCH v2] ALSA: ctxfi: Simplify dao_clear_{left,right}_input() functions Ethan Carter Edwards
2024-12-30 15:40 ` Ethan Carter Edwards
2024-12-30 15:47 ` Kuan-Wei Chiu [this message]
2024-12-30 18:11 ` David Laight

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=Z3LAfa0cIY2eboNR@visitorckw-System-Product-Name \
    --to=visitorckw@gmail.com \
    --cc=arnd@arndb.de \
    --cc=david.laight.linux@gmail.com \
    --cc=ethan@ethancedwards.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=ryan_richards@creativelabs.com \
    --cc=tiwai@suse.com \
    --cc=tiwai@suse.de \
    --cc=wychay@ctl.creative.com \
    /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