From: Allen <allen.lkml@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Kees Cook <keescook@chromium.org>,
timur@kernel.org, Xiubo.Lee@gmail.com,
Takashi Iwai <tiwai@suse.de>,
linux-kernel@vger.kernel.org, clemens@ladisch.de, tiwai@suse.com,
nicoleotsuka@gmail.com, Allen Pais <allen.cryptic@gmail.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 00/10] sound: convert tasklets to use new tasklet_setup()
Date: Wed, 19 Aug 2020 16:21:58 +0530 [thread overview]
Message-ID: <CAOMdWSK79WWsmsxJH9zUMZMfkBNRWXbmEHg-haxNZopHjC1cGw@mail.gmail.com> (raw)
In-Reply-To: <20200818104432.GB5337@sirena.org.uk>
>
> > Mark, may I apply those ASoC patches through my tree together with
> > others? Those seem targeting to 5.9, and I have a patch set to
> > convert to tasklet for 5.10, which would be better manageable when
> > based on top of those changes.
>
> These patches which I wasn't CCed on and which need their subject lines
> fixing :( . With the subject lines fixed I guess so so
Extremely sorry. I thought I had it covered. How would you like it
worded?
> Acked-by: Mark Brown <broonie@kernel.org>
>
> but judging from some of the other threads about similar patches that I
> was randomly CCed on I'm not sure people like from_tasklet() so perhaps
> there might be issues.
Yes, there is a new macro by name cast_out() is suggested in place of
from_tasklet(). Hopefully it will go in soon. Will spin out V2 with the change
and also re-word subject line.
> Allen, as documented in submitting-patches.rst please send patches to
> the maintainers for the code you would like to change. The normal
> kernel workflow is that people apply patches from their inboxes, if they
> aren't copied they are likely to not see the patch at all and it is much
> more difficult to apply patches.
I understand, I'll take care of it in the future. Thank you.
--
- Allen
next prev parent reply other threads:[~2020-08-19 10:53 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
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 [this message]
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=CAOMdWSK79WWsmsxJH9zUMZMfkBNRWXbmEHg-haxNZopHjC1cGw@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=broonie@kernel.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=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).