All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>
Subject: Re: [PATCH v1 1/1] ALSA: control: Use list_for_each_entry_safe()
Date: Tue, 29 Aug 2023 17:16:32 +0300	[thread overview]
Message-ID: <ZO39wMfKDmXc1+ms@smile.fi.intel.com> (raw)
In-Reply-To: <87ttsit08x.wl-tiwai@suse.de>

On Tue, Aug 29, 2023 at 04:02:38PM +0200, Takashi Iwai wrote:
> On Tue, 29 Aug 2023 15:52:52 +0200,
> Andy Shevchenko wrote:
> > 
> > Instead of reiterating the list, use list_for_each_entry_safe()
> > that allows to continue without starting over.

> Through a quick glance, it should be OK, but I need to read and
> understand whether this change is perfectly safe or not -- unless
> Jaroslav gives his review and ack.

Sure.

> > ---
> > 
> > Takashi, if you have anybody or want yourself to spend some time,
> > I believe you can simplify a lot the parser in this file with
> > the help of lib/cmdline.c APIs.
> 
> Thanks for the hint.  Yeah, it looks feasible, but too late for 6.6,
> it's a nice TODO ;)

Of course.

Just a reference what I did to gpio-aggregator module:
ac505b6f5fa8 ("gpio: aggregator: Replace custom get_arg() with a generic next_arg()")
deb631c40114 ("gpio: aggregator: Replace isrange() by using get_options()")


-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2023-08-29 14:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-29 13:52 [PATCH v1 1/1] ALSA: control: Use list_for_each_entry_safe() Andy Shevchenko
2023-08-29 14:02 ` Takashi Iwai
2023-08-29 14:16   ` Andy Shevchenko [this message]
2023-08-29 14:10 ` Jaroslav Kysela
2023-08-29 14:20   ` Andy Shevchenko
2023-08-29 15:55 ` kernel test robot

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=ZO39wMfKDmXc1+ms@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.com \
    --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 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.