From: Richard Weinberger <richard@nod.at>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: masahiroy <masahiroy@kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
kernel test robot <lkp@intel.com>,
anton ivanov <anton.ivanov@cambridgegreys.com>,
Johannes Berg <johannes@sipsolutions.net>,
linux-um <linux-um@lists.infradead.org>, tj <tj@kernel.org>,
Takashi Iwai <tiwai@suse.de>, Jaroslav Kysela <perex@perex.cz>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Nicolas Schier <nicolas@fjasle.eu>,
linux-kbuild <linux-kbuild@vger.kernel.org>,
alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: [PATCH v3] um/drivers: fix hostaudio build errors
Date: Mon, 31 Jul 2023 07:27:54 +0200 (CEST) [thread overview]
Message-ID: <1063472755.889096.1690781274039.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <3cd0e5b7-7e20-ce3b-e391-eb77443f63b1@infradead.org>
----- Ursprüngliche Mail -----
> Von: "Randy Dunlap" <rdunlap@infradead.org>
> Oh, good point, and one that I agree with.
>
> I'll send a v4.
Ok!
>>
>> Reviewed-by: Masahiro Yamada <masahiroy@kernel.org>
>
> Takashi, I don't know who will merge the patch, but I would expect
> that one of the UML maintainers to merge it.... FWIW.
Yep. I'll carry this fix (v4) through the uml tree.
Thanks,
//richard
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
prev parent reply other threads:[~2023-07-31 5:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 4:30 [PATCH v3] um/drivers: fix hostaudio build errors Randy Dunlap
2023-07-28 6:40 ` Takashi Iwai
2023-07-28 8:51 ` Masahiro Yamada
2023-07-31 2:38 ` Randy Dunlap
2023-07-31 5:27 ` Richard Weinberger [this message]
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=1063472755.889096.1690781274039.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=alsa-devel@alsa-project.org \
--cc=anton.ivanov@cambridgegreys.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=lkp@intel.com \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nicolas@fjasle.eu \
--cc=perex@perex.cz \
--cc=rdunlap@infradead.org \
--cc=tiwai@suse.de \
--cc=tj@kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).