From: Allen <allen.lkml@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, Kees Cook <keescook@chromium.org>,
timur@kernel.org, Xiubo.Lee@gmail.com,
linux-kernel@vger.kernel.org, clemens@ladisch.de, tiwai@suse.com,
o-takashi@sakamocchi.jp, nicoleotsuka@gmail.com,
Allen Pais <allen.cryptic@gmail.com>,
perex@perex.cz, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 00/10] sound: convert tasklets to use new tasklet_setup()
Date: Tue, 18 Aug 2020 15:01:56 +0530 [thread overview]
Message-ID: <CAOMdWSLJmiAxH5bvwh9b8O_MLdttU3Fsb4B_Y2tA08_P1b0BXQ@mail.gmail.com> (raw)
In-Reply-To: <s5hk0xxppz6.wl-tiwai@suse.de>
>
> Well, then at the next time, please mention it explicitly in the cover
> letter. Usually this kind of API conversion isn't done during rc. Or
> it's done systematically via script or such. So unless mentioned,
> it's not expected to be carried to 5.9.
Sorry for having missed the detail. Will take care of it in the future.
>
> In anyway, if the final purpose is to drop the old tasklet API and
> that's the plan for 5.9, all tree-wide changes have to be done in
> 5.9 beforehand. Was that the decision?
The idea was to land the tree-wide changes as part of 5.9
>
> > > I have a patch set to drop the whole tasklet usage in sound/*
> > > (destined for 5.10, to be submitted soon), so if that's for 5.10,
> > > it'll be likely superfluous.
> >
> > I have picked patches from your tree to adapt to this new API.
> > Those can be picked in 5.10 I suppose.
>
> Adapting the changes are trivial, don't worry. It was just a question
> of how to organize changes.
Sure, Thank you.
- Allen
next prev parent reply other threads:[~2020-08-18 9:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 8:56 [PATCH 00/10] sound: convert tasklets to use new tasklet_setup() Allen Pais
2020-08-17 8:56 ` [PATCH 01/10] sound: core: convert tasklets to use new tasklet_setup() API Allen Pais
2020-08-17 8:56 ` [PATCH 02/10] sound: firewire: " Allen Pais
2020-08-17 8:56 ` [PATCH 03/10] sound: asihpi: " Allen Pais
2020-08-17 8:56 ` [PATCH 04/10] sound: riptide: " Allen Pais
2020-08-17 8:56 ` [PATCH 05/10] sound: rm9652: " Allen Pais
2020-08-17 8:56 ` [PATCH 06/10] sound/soc: fsl_esai: " Allen Pais
2020-08-17 8:57 ` [PATCH 07/10] sound/soc: sh: " Allen Pais
2020-08-17 8:57 ` [PATCH 08/10] sound/soc: txx9: " Allen Pais
2020-08-17 8:57 ` [PATCH 09/10] sound: midi: " Allen Pais
2020-08-17 8:57 ` [PATCH 10/10] sound: ua101: " Allen Pais
2020-08-17 9:08 ` [PATCH 00/10] sound: convert tasklets to use new tasklet_setup() Takashi Iwai
2020-08-17 9:18 ` Allen Pais
2020-08-17 9:43 ` Takashi Iwai
2020-08-18 9:31 ` Allen [this message]
2020-08-18 10:25 ` Takashi Iwai
2020-08-18 10:44 ` Mark Brown
2020-08-18 10:59 ` Takashi Iwai
2020-08-19 10:51 ` Allen
2020-08-19 11:16 ` Mark Brown
2020-08-19 11:28 ` Takashi Iwai
2020-09-01 10:04 ` Allen
2020-09-01 10:09 ` 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=CAOMdWSLJmiAxH5bvwh9b8O_MLdttU3Fsb4B_Y2tA08_P1b0BXQ@mail.gmail.com \
--to=allen.lkml@gmail.com \
--cc=Xiubo.Lee@gmail.com \
--cc=allen.cryptic@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nicoleotsuka@gmail.com \
--cc=o-takashi@sakamocchi.jp \
--cc=perex@perex.cz \
--cc=timur@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).