From: Takashi Iwai <tiwai@suse.de>
To: Kees Cook <keescook@chromium.org>
Cc: moderated for non-subscribers <alsa-devel@alsa-project.org>,
LKML <linux-kernel@vger.kernel.org>,
Mark Brown <broonie@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Bhumika Goyal <bhumirks@gmail.com>
Subject: Re: [PATCH] ALSA: sh: aica: Convert timers to use timer_setup()
Date: Thu, 05 Oct 2017 19:19:06 +0200 [thread overview]
Message-ID: <s5hinftpl6d.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAGXu5jJsq3Nbu5hZc5S=PCG+2LiH+n7NMZ3xv=e5nhEwcjrRtA@mail.gmail.com>
On Thu, 05 Oct 2017 19:17:16 +0200,
Kees Cook wrote:
>
> On Wed, Oct 4, 2017 at 11:22 PM, Takashi Iwai <tiwai@suse.de> wrote:
> > On Thu, 05 Oct 2017 02:53:36 +0200,
> > Kees Cook wrote:
> >>
> >> In preparation for unconditionally passing the struct timer_list pointer to
> >> all timer callbacks, switch to using the new timer_setup() and from_timer()
> >> to pass the timer pointer explicitly. This requires adding a pointer to
> >> hold the timer's target substream, as there won't be a way to pass this in
> >> the future.
> >>
> >> Cc: Jaroslav Kysela <perex@perex.cz>
> >> Cc: Takashi Iwai <tiwai@suse.com>
> >> Cc: Bhumika Goyal <bhumirks@gmail.com>
> >> Cc: Mark Brown <broonie@kernel.org>
> >> Cc: alsa-devel@alsa-project.org
> >> Cc: Thomas Gleixner <tglx@linutronix.de>
> >> Signed-off-by: Kees Cook <keescook@chromium.org>
> >> ---
> >> This requires commit 686fef928bba ("timer: Prepare to change timer
> >> callback argument type") in v4.14-rc3, but should be otherwise
> >> stand-alone.
> >
> > The conversions look straightforward, so I'm going to apply it (and
> > other two you posted). But now I wonder why only three were chosen.
> > Will you keep working on the rest usages in sound/*, or would you
> > expect us doing the rest?
>
> Hi, thanks for applying them!
>
> I'm working my way through the "non-trivial" changes first. I have a
> coccinelle script that will do a mass-conversion of the common cases.
> It's possible that those changes cover the other usages in sound/* or
> that I haven't made my way through the others yet (it's a very long
> list). I wouldn't object to other people helping with the conversions,
> of course. :)
OK, scripting is a better way, then I'd save my time and wait until
you get more systematic coverage, then :)
thanks,
Takashi
WARNING: multiple messages have this Message-ID (diff)
From: Takashi Iwai <tiwai@suse.de>
To: Kees Cook <keescook@chromium.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
moderated for non-subscribers <alsa-devel@alsa-project.org>,
Bhumika Goyal <bhumirks@gmail.com>,
Mark Brown <broonie@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Jaroslav Kysela <perex@perex.cz>
Subject: Re: [PATCH] ALSA: sh: aica: Convert timers to use timer_setup()
Date: Thu, 05 Oct 2017 19:19:06 +0200 [thread overview]
Message-ID: <s5hinftpl6d.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAGXu5jJsq3Nbu5hZc5S=PCG+2LiH+n7NMZ3xv=e5nhEwcjrRtA@mail.gmail.com>
On Thu, 05 Oct 2017 19:17:16 +0200,
Kees Cook wrote:
>
> On Wed, Oct 4, 2017 at 11:22 PM, Takashi Iwai <tiwai@suse.de> wrote:
> > On Thu, 05 Oct 2017 02:53:36 +0200,
> > Kees Cook wrote:
> >>
> >> In preparation for unconditionally passing the struct timer_list pointer to
> >> all timer callbacks, switch to using the new timer_setup() and from_timer()
> >> to pass the timer pointer explicitly. This requires adding a pointer to
> >> hold the timer's target substream, as there won't be a way to pass this in
> >> the future.
> >>
> >> Cc: Jaroslav Kysela <perex@perex.cz>
> >> Cc: Takashi Iwai <tiwai@suse.com>
> >> Cc: Bhumika Goyal <bhumirks@gmail.com>
> >> Cc: Mark Brown <broonie@kernel.org>
> >> Cc: alsa-devel@alsa-project.org
> >> Cc: Thomas Gleixner <tglx@linutronix.de>
> >> Signed-off-by: Kees Cook <keescook@chromium.org>
> >> ---
> >> This requires commit 686fef928bba ("timer: Prepare to change timer
> >> callback argument type") in v4.14-rc3, but should be otherwise
> >> stand-alone.
> >
> > The conversions look straightforward, so I'm going to apply it (and
> > other two you posted). But now I wonder why only three were chosen.
> > Will you keep working on the rest usages in sound/*, or would you
> > expect us doing the rest?
>
> Hi, thanks for applying them!
>
> I'm working my way through the "non-trivial" changes first. I have a
> coccinelle script that will do a mass-conversion of the common cases.
> It's possible that those changes cover the other usages in sound/* or
> that I haven't made my way through the others yet (it's a very long
> list). I wouldn't object to other people helping with the conversions,
> of course. :)
OK, scripting is a better way, then I'd save my time and wait until
you get more systematic coverage, then :)
thanks,
Takashi
next prev parent reply other threads:[~2017-10-05 17:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 0:53 [PATCH] ALSA: sh: aica: Convert timers to use timer_setup() Kees Cook
2017-10-05 6:22 ` Takashi Iwai
2017-10-05 6:22 ` Takashi Iwai
2017-10-05 17:17 ` Kees Cook
2017-10-05 17:19 ` Takashi Iwai [this message]
2017-10-05 17:19 ` 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=s5hinftpl6d.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=bhumirks@gmail.com \
--cc=broonie@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.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.