From: Takashi Iwai <tiwai@suse.de>
To: Ethan Carter Edwards <ethan@ethancedwards.com>
Cc: "wychay@ctl.creative.com" <wychay@ctl.creative.com>,
"ryan_richards@creativelabs.com" <ryan_richards@creativelabs.com>,
"tiwai@suse.de" <tiwai@suse.de>,
"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: sound/pci/ctxfi/ctdaio.c: duplicate function removal question
Date: Sun, 29 Dec 2024 09:32:20 +0100 [thread overview]
Message-ID: <87plladh4b.wl-tiwai@suse.de> (raw)
In-Reply-To: <NyKCr2VHK_xCQDwNxFKKx2LVd2d_AC2f2j4eAvnD9uRPtb50i2AruCLOp6mHxsGiyYJ0Tgd3Z50Oy1JTi5gPhjd2WQM2skrv7asp3fLl8HU=@ethancedwards.com>
On Wed, 25 Dec 2024 00:16:17 +0100,
Ethan Carter Edwards wrote:
>
> Hello all,
>
> First of all, happy holidays.
>
> I was browsing the ctdaio.c code and I noticed a lot of
> duplicate code and functions, specifically:
>
> dao_set_{right,left}_input and
> dao_clear_{right,left}_input functions.
>
> The functions are pretty much identical. They only
> differ in the side (left, right). What was the original
> idea in doing this? Wouldn't it make more since to just
> have an ENUM (left, right) as an argument that would
> determine the side and just reduce the function to
> dao_set_input and dao_clear_input.
>
> I would be more than happy to send in a patch doing
> these changes, but before I did I wanted to ask if
> there was a reason the code was written in this way.
> I am pretty new to kernel development.
Yes, the code simplification would be appreciated.
You can create a common function and call with the left/right
argument from each callback or change the call pattern from ctatc.c.
thanks,
Takashi
next prev parent reply other threads:[~2024-12-29 8:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-24 23:16 sound/pci/ctxfi/ctdaio.c: duplicate function removal question Ethan Carter Edwards
2024-12-29 8:32 ` Takashi Iwai [this message]
2024-12-29 9:02 ` David Laight
2024-12-29 9:10 ` Takashi Iwai
2024-12-29 10:57 ` David Laight
2024-12-29 12:03 ` Takashi Iwai
2024-12-29 13:34 ` David Laight
2024-12-30 15:53 ` Ethan Carter Edwards
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=87plladh4b.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=ethan@ethancedwards.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=ryan_richards@creativelabs.com \
--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