From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: alsa-devel@alsa-project.org, tiwai@suse.de,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
broonie@kernel.org, srinivas.kandagatla@linaro.org,
jank@cadence.com, slawomir.blauciak@intel.com,
Sanyog Kale <sanyog.r.kale@intel.com>,
Bard liao <yung-chuan.liao@linux.intel.com>,
Rander Wang <rander.wang@linux.intel.com>
Subject: Re: [alsa-devel] [PATCH 1/4] soundwire: sdw_slave: add new fields to track probe status
Date: Fri, 8 Nov 2019 08:55:41 -0600 [thread overview]
Message-ID: <e3e10c25-84dc-f4e7-e94b-d18493450021@linux.intel.com> (raw)
In-Reply-To: <20191108042940.GW952516@vkoul-mobl>
On 11/7/19 10:29 PM, Vinod Koul wrote:
> On 04-11-19, 08:32, Pierre-Louis Bossart wrote:
>>
>>
>> On 11/2/19 11:56 PM, Vinod Koul wrote:
>>> On 23-10-19, 16:06, Pierre-Louis Bossart wrote:
>>>> Changes to the sdw_slave structure needed to solve race conditions on
>>>> driver probe.
>>>
>>> Can you please explain the race you have observed, it would be a very
>>> useful to document it as well
>>
>> the races are explained in the [PATCH 00/18] soundwire: code hardening and
>> suspend-resume support series.
>
> It would make sense to explain it here as well to give details to
> reviewers, there is nothing wrong with too much detail!
>
>>>>
>>>> The functionality is added in the next patch.
>>>
>>> which one..?
>>
>> [PATCH 00/18] soundwire: code hardening and suspend-resume support
>
> Yeah great! let me play detective with 18 patch series. I asked for a
> patch and got a series!
>
> Again, please help the maintainer to help you. We would love to see this
> merged as well, but please step up and give more details in cover
> letter and changelogs. I shouldn't need to do guesswork and scan through the
> inbox to find the context!
We are clearly not going anywhere.
I partitioned the patches to make your maintainer life easier and help
the integration of SoundWire across two trees. All I get is negative
feedback, grand-standing, and zero comments on actual changes.
For the record, I am mindful of reviewer/maintainer workload, and I did
contact you in September to check your availability and provided a
pointer to initial code changes. I did send a first version a week prior
to your travel/vacation, I resend another version when you were back and
waited yet another two weeks to resend a second version. I also
contacted Takashi, Mark and you to suggest this code partition, and did
not get any pushback. It's not like I am pushing stuff down your throat,
I have been patient and considerate.
Please start with the patches "soundwire: code hardening and
suspend-resume support" and come back to this interface description when
you have reviewed these changes. It's not detective work, it's working
around the consequences of having separate trees for Audio and SoundWire.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-11-08 15:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 21:06 [alsa-devel] [PATCH 0/4] soundwire: update ASoC interfaces Pierre-Louis Bossart
2019-10-23 21:06 ` [alsa-devel] [PATCH 1/4] soundwire: sdw_slave: add new fields to track probe status Pierre-Louis Bossart
2019-11-03 4:56 ` Vinod Koul
2019-11-04 14:32 ` Pierre-Louis Bossart
2019-11-08 4:29 ` Vinod Koul
2019-11-08 14:55 ` Pierre-Louis Bossart [this message]
2019-11-08 20:26 ` Liam Girdwood
2019-11-09 11:12 ` Vinod Koul
2019-11-11 16:34 ` Pierre-Louis Bossart
2019-11-14 11:50 ` Vinod Koul
2019-11-14 15:14 ` Pierre-Louis Bossart
2019-10-23 21:06 ` [alsa-devel] [PATCH 2/4] soundwire: add enumeration_complete structure Pierre-Louis Bossart
2019-11-03 5:22 ` Vinod Koul
2019-11-04 14:32 ` Pierre-Louis Bossart
2019-10-23 21:06 ` [alsa-devel] [PATCH 3/4] soundwire: intel: update interfaces between ASoC and SoundWire Pierre-Louis Bossart
2019-10-23 21:06 ` [alsa-devel] [PATCH 4/4] soundwire: intel: update stream callbacks for hwparams/free stream operations Pierre-Louis Bossart
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=e3e10c25-84dc-f4e7-e94b-d18493450021@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jank@cadence.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rander.wang@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=sanyog.r.kale@intel.com \
--cc=slawomir.blauciak@intel.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=tiwai@suse.de \
--cc=vkoul@kernel.org \
--cc=yung-chuan.liao@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: 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).