lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Tue, 8 Sep 2020 10:33:19 -0500
From:   Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>
To:     Mark Brown <broonie@...nel.org>
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



>>>>> 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.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ