From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Jaroslav Kysela <perex@perex.cz>,
alsa-devel@alsa-project.org, tiwai@suse.de,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
hui.wang@canonical.com, Vinod Koul <vkoul@kernel.org>,
srinivas.kandagatla@linaro.org,
ranjani.sridharan@linux.intel.com, jank@cadence.com,
mengdong.lin@intel.com, sanyog.r.kale@intel.com,
Bard Liao <yung-chuan.liao@linux.intel.com>,
rander.wang@linux.intel.com, bard.liao@intel.com
Subject: Re: [PATCH 1/7] soundwire: bus: use property to set interrupt masks
Date: Tue, 8 Sep 2020 10:33:19 -0500 [thread overview]
Message-ID: <973b1a09-40a9-1d10-4975-3f6d5a9340b1@linux.intel.com> (raw)
In-Reply-To: <20200908151412.GE5551@sirena.org.uk>
>>>>> I don't have this patch and since I seem to get copied on quite a lot of
>>>>> soundwire only serieses I just delete them unread mostly.
>
>> We now try to use the ASoC/SoundWire prefix for cover letters to highlight
>> that a patchset changes things across two trees, does this help or do we
>> need a different way of flagging these patches?
>
> I think the issue is mainly where the patch itself touches both, if some
> of the patches mention ASoC I'll generally notice them but Soundwire is
> one of these things I get so many random CCs for I just zone it out so
> highlighting the individual patches would help.
ok, we'll highlight individual patches then and better explain dependencies.
next prev parent reply other threads:[~2020-09-08 20:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 14:06 [PATCH 0/7] soundwire: filter out invalid PARITY errors Bard Liao
2020-08-18 14:06 ` [PATCH 1/7] soundwire: bus: use property to set interrupt masks Bard Liao
2020-08-28 6:51 ` Vinod Koul
2020-09-08 12:05 ` Jaroslav Kysela
2020-09-08 12:11 ` Mark Brown
2020-09-08 12:28 ` Jaroslav Kysela
2020-09-08 14:33 ` Mark Brown
2020-09-08 14:43 ` Jaroslav Kysela
2020-09-08 14:47 ` Pierre-Louis Bossart
2020-09-08 15:14 ` Mark Brown
2020-09-08 15:33 ` Pierre-Louis Bossart [this message]
2020-08-18 14:06 ` [PATCH 2/7] soundwire: bus: filter-out unwanted interrupt reports Bard Liao
2020-08-18 14:06 ` [PATCH 3/7] soundwire: slave: add first_interrupt_done status Bard Liao
2020-08-18 14:06 ` [PATCH 4/7] soundwire: bus: use quirk to filter out invalid parity errors Bard Liao
2020-08-18 14:06 ` [PATCH 5/7] ASoC: codecs: realtek-soundwire: ignore initial PARITY errors Bard Liao
2020-08-19 8:39 ` Mark Brown
2020-08-18 14:06 ` [PATCH 6/7] soundwire: bus: export broadcast read/write capability for tests Bard Liao
2020-08-18 14:06 ` [PATCH 7/7] soundwire: cadence: add parity error injection through debugfs Bard Liao
2020-09-08 12:07 ` [PATCH 0/7] soundwire: filter out invalid PARITY errors Jaroslav Kysela
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=973b1a09-40a9-1d10-4975-3f6d5a9340b1@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hui.wang@canonical.com \
--cc=jank@cadence.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mengdong.lin@intel.com \
--cc=perex@perex.cz \
--cc=rander.wang@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=sanyog.r.kale@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).