From: Hans de Goede <hdegoede@redhat.com> To: Lee Jones <lee.jones@linaro.org> Cc: Cezary Rojewski <cezary.rojewski@intel.com>, Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>, Liam Girdwood <liam.r.girdwood@linux.intel.com>, Jie Yang <yang.jie@linux.intel.com>, Mark Brown <broonie@kernel.org>, patches@opensource.cirrus.com, linux-kernel@vger.kernel.org, Andy Shevchenko <andy.shevchenko@gmail.com>, Charles Keepax <ckeepax@opensource.cirrus.com>, alsa-devel@alsa-project.org Subject: Re: [PATCH v4 0/5] MFD/ASoC: Add support for Intel Bay Trail boards with WM5102 codec Date: Thu, 4 Feb 2021 12:07:49 +0100 [thread overview] Message-ID: <7f53dede-946e-c38e-e871-3df1119f1faf@redhat.com> (raw) In-Reply-To: <20210204105748.GD2789116@dell> Hi, On 2/4/21 11:57 AM, Lee Jones wrote: > On Thu, 04 Feb 2021, Hans de Goede wrote: > >> Hi all, >> >> On 1/20/21 10:49 PM, Hans de Goede wrote: >>> Hi All, >>> >>> Here is v4 of my series to add support for Intel Bay Trail based devices >>> which use a WM5102 codec for audio output/input. >>> >>> This was developed and tested on a Lenovo Yoga Tablet 1051L. >>> >>> The MFD and ASoC parts do not have any build-time dependencies >>> on each other. But the follow-up jack-detect series does have >>> patches depending on each-other and on this series. So IMHO it >>> would be best if this entire series would be merged through the >>> MFD tree to make merging the follow-up series easier. >>> >>> Mark, if that is ok with you (and you are happy with the ASoC >>> changes) can you please Ack this ? >> >> I believe that this series and the follow-up: >> >> "[PATCH v4 00/13] MFD/extcon/ASoC: Rework arizona codec jack-detect support" >> >> series are both ready for merging. All patches have Reviewed-by and/or >> Acked-by tags now. > > I don't think they do. You're missing ASoC and Extcon Acks. Right, what I meant is that the patches have been reviewed by other stake-holders, including the follow-up series being tested by the cirrus codec folks (thank you Charles). But yes the actual subsys maintainers have not acked these yet; and I'm aware that you will need those for merging this through the MFD tree. Note that this series only requires Mark ack, the follow-up also touches extcon code, this one is purely MFD + ASoC patches. > Not sure why *this* set fell through the cracks though. However, it's > now on my to-review list. > > If I can work fast enough, maybe this series can get into 5.12, but > the follow-up still needs reviews. > > It might be best to collect the *-bys you do have and [RESEND]. Ok, will do. >> I guess it is too late for 5.12, but it would be nice to at least formulate >> a plan for getting this merged after 5.12-rc1 is out. Given the >> interdependencies I still believe that it is best to merge all the patches >> through the mfd tree and then have Lee provide an immutable branch for the >> other subsystems to merge. > > Yes, that's fine. > >> Mark and extcon-maintainers (for the follow-up series) may we have your ack >> for merging these through the MFD tree ? > > Ah, you noticed that too! Ack :) Regards, Hans
WARNING: multiple messages have this Message-ID (diff)
From: Hans de Goede <hdegoede@redhat.com> To: Lee Jones <lee.jones@linaro.org> Cc: Cezary Rojewski <cezary.rojewski@intel.com>, Charles Keepax <ckeepax@opensource.cirrus.com>, alsa-devel@alsa-project.org, patches@opensource.cirrus.com, Jie Yang <yang.jie@linux.intel.com>, Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>, linux-kernel@vger.kernel.org, Liam Girdwood <liam.r.girdwood@linux.intel.com>, Andy Shevchenko <andy.shevchenko@gmail.com>, Mark Brown <broonie@kernel.org> Subject: Re: [PATCH v4 0/5] MFD/ASoC: Add support for Intel Bay Trail boards with WM5102 codec Date: Thu, 4 Feb 2021 12:07:49 +0100 [thread overview] Message-ID: <7f53dede-946e-c38e-e871-3df1119f1faf@redhat.com> (raw) In-Reply-To: <20210204105748.GD2789116@dell> Hi, On 2/4/21 11:57 AM, Lee Jones wrote: > On Thu, 04 Feb 2021, Hans de Goede wrote: > >> Hi all, >> >> On 1/20/21 10:49 PM, Hans de Goede wrote: >>> Hi All, >>> >>> Here is v4 of my series to add support for Intel Bay Trail based devices >>> which use a WM5102 codec for audio output/input. >>> >>> This was developed and tested on a Lenovo Yoga Tablet 1051L. >>> >>> The MFD and ASoC parts do not have any build-time dependencies >>> on each other. But the follow-up jack-detect series does have >>> patches depending on each-other and on this series. So IMHO it >>> would be best if this entire series would be merged through the >>> MFD tree to make merging the follow-up series easier. >>> >>> Mark, if that is ok with you (and you are happy with the ASoC >>> changes) can you please Ack this ? >> >> I believe that this series and the follow-up: >> >> "[PATCH v4 00/13] MFD/extcon/ASoC: Rework arizona codec jack-detect support" >> >> series are both ready for merging. All patches have Reviewed-by and/or >> Acked-by tags now. > > I don't think they do. You're missing ASoC and Extcon Acks. Right, what I meant is that the patches have been reviewed by other stake-holders, including the follow-up series being tested by the cirrus codec folks (thank you Charles). But yes the actual subsys maintainers have not acked these yet; and I'm aware that you will need those for merging this through the MFD tree. Note that this series only requires Mark ack, the follow-up also touches extcon code, this one is purely MFD + ASoC patches. > Not sure why *this* set fell through the cracks though. However, it's > now on my to-review list. > > If I can work fast enough, maybe this series can get into 5.12, but > the follow-up still needs reviews. > > It might be best to collect the *-bys you do have and [RESEND]. Ok, will do. >> I guess it is too late for 5.12, but it would be nice to at least formulate >> a plan for getting this merged after 5.12-rc1 is out. Given the >> interdependencies I still believe that it is best to merge all the patches >> through the mfd tree and then have Lee provide an immutable branch for the >> other subsystems to merge. > > Yes, that's fine. > >> Mark and extcon-maintainers (for the follow-up series) may we have your ack >> for merging these through the MFD tree ? > > Ah, you noticed that too! Ack :) Regards, Hans
next prev parent reply other threads:[~2021-02-04 11:09 UTC|newest] Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-20 21:49 [PATCH v4 0/5] MFD/ASoC: Add support for Intel Bay Trail boards with WM5102 codec Hans de Goede 2021-01-20 21:49 ` Hans de Goede 2021-01-20 21:49 ` [PATCH v4 1/5] mfd: arizona: Add MODULE_SOFTDEP("pre: arizona_ldo1") Hans de Goede 2021-01-20 21:49 ` Hans de Goede 2021-02-04 13:55 ` Lee Jones 2021-02-04 13:55 ` Lee Jones 2021-01-20 21:49 ` [PATCH v4 2/5] mfd: arizona: Replace arizona_of_get_type() with device_get_match_data() Hans de Goede 2021-01-20 21:49 ` Hans de Goede 2021-02-04 13:55 ` Lee Jones 2021-02-04 13:55 ` Lee Jones 2021-01-20 21:49 ` [PATCH v4 3/5] mfd: arizona: Add support for ACPI enumeration of WM5102 connected over SPI Hans de Goede 2021-01-20 21:49 ` Hans de Goede 2021-01-21 10:34 ` Charles Keepax 2021-01-21 10:34 ` Charles Keepax 2021-02-04 13:55 ` Lee Jones 2021-02-04 13:55 ` Lee Jones 2021-01-20 21:49 ` [PATCH v4 4/5] ASoC: Intel: Add DMI quirk table to soc_intel_is_byt_cr() Hans de Goede 2021-01-20 21:49 ` Hans de Goede 2021-02-04 13:56 ` Lee Jones 2021-02-04 13:56 ` Lee Jones 2021-02-04 14:05 ` Mark Brown 2021-02-04 14:05 ` Mark Brown 2021-02-04 15:04 ` Lee Jones 2021-02-04 15:04 ` Lee Jones 2021-02-04 15:11 ` Mark Brown 2021-02-04 15:11 ` Mark Brown 2021-02-04 15:40 ` Lee Jones 2021-02-04 15:40 ` Lee Jones 2021-02-04 19:42 ` Mark Brown 2021-02-04 19:42 ` Mark Brown 2021-02-05 8:34 ` Lee Jones 2021-02-05 8:34 ` Lee Jones 2021-02-05 21:11 ` Mark Brown 2021-02-05 21:11 ` Mark Brown 2021-02-08 8:33 ` Lee Jones 2021-02-08 8:33 ` Lee Jones 2021-02-08 15:24 ` Mark Brown 2021-02-08 15:24 ` Mark Brown 2021-01-20 21:49 ` [PATCH v4 5/5] ASoC: Intel: bytcr_wm5102: Add machine driver for BYT/WM5102 Hans de Goede 2021-01-20 21:49 ` Hans de Goede 2021-01-21 10:37 ` Charles Keepax 2021-01-21 10:37 ` Charles Keepax 2021-02-04 13:56 ` Lee Jones 2021-02-04 13:56 ` Lee Jones 2021-02-04 10:25 ` [PATCH v4 0/5] MFD/ASoC: Add support for Intel Bay Trail boards with WM5102 codec Hans de Goede 2021-02-04 10:25 ` Hans de Goede 2021-02-04 10:57 ` Lee Jones 2021-02-04 10:57 ` Lee Jones 2021-02-04 11:07 ` Hans de Goede [this message] 2021-02-04 11:07 ` Hans de Goede 2021-02-04 12:43 ` Mark Brown 2021-02-04 12:43 ` Mark Brown 2021-02-04 13:18 ` Hans de Goede 2021-02-04 13:18 ` Hans de Goede 2021-02-04 14:04 ` Mark Brown 2021-02-04 14:04 ` Mark Brown 2021-02-04 13:46 ` Lee Jones 2021-02-04 13:46 ` Lee Jones 2021-02-04 15:09 ` Mark Brown 2021-02-04 15:09 ` Mark Brown 2021-02-04 15:21 ` Lee Jones 2021-02-04 15:21 ` Lee Jones 2021-02-04 16:48 ` Mark Brown 2021-02-04 16:48 ` Mark Brown 2021-02-08 13:52 ` [GIT PULL] Immutable branch from MFD due for the v5.12 merge window Lee Jones 2021-02-08 13:52 ` Lee Jones 2021-02-08 18:38 ` (subset) [PATCH v4 0/5] MFD/ASoC: Add support for Intel Bay Trail boards with WM5102 codec Mark Brown 2021-02-08 18:38 ` Mark Brown 2021-02-08 19:12 ` Hans de Goede 2021-02-08 19:12 ` Hans de Goede
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=7f53dede-946e-c38e-e871-3df1119f1faf@redhat.com \ --to=hdegoede@redhat.com \ --cc=alsa-devel@alsa-project.org \ --cc=andy.shevchenko@gmail.com \ --cc=broonie@kernel.org \ --cc=cezary.rojewski@intel.com \ --cc=ckeepax@opensource.cirrus.com \ --cc=lee.jones@linaro.org \ --cc=liam.r.girdwood@linux.intel.com \ --cc=linux-kernel@vger.kernel.org \ --cc=patches@opensource.cirrus.com \ --cc=pierre-louis.bossart@linux.intel.com \ --cc=yang.jie@linux.intel.com \ /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: linkBe 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.