[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200908151412.GE5551@sirena.org.uk>
Date: Tue, 8 Sep 2020 16:14:13 +0100
From: Mark Brown <broonie@...nel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>
Cc: Jaroslav Kysela <perex@...ex.cz>, alsa-devel@...a-project.org,
tiwai@...e.de, gregkh@...uxfoundation.org,
linux-kernel@...r.kernel.org, hui.wang@...onical.com,
Vinod Koul <vkoul@...nel.org>, srinivas.kandagatla@...aro.org,
ranjani.sridharan@...ux.intel.com, jank@...ence.com,
mengdong.lin@...el.com, sanyog.r.kale@...el.com,
Bard Liao <yung-chuan.liao@...ux.intel.com>,
rander.wang@...ux.intel.com, bard.liao@...el.com
Subject: Re: [PATCH 1/7] soundwire: bus: use property to set interrupt masks
On Tue, Sep 08, 2020 at 09:47:13AM -0500, Pierre-Louis Bossart wrote:
> On 9/8/20 9:33 AM, Mark Brown wrote:
> > On Tue, Sep 08, 2020 at 02:28:48PM +0200, Jaroslav Kysela wrote:
> > > Dne 08. 09. 20 v 14:11 Mark Brown napsal(a):
> > > > 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.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists