linux-kernel - Re: [PATCH] ASoC: Intel: kbl_rt5663_max98927: Fix kabylake_ssp

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:   Mon, 26 Oct 2020 23:10:51 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Tomasz Figa <tfiga@...omium.org>
Cc:     alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
        Cezary Rojewski <cezary.rojewski@...el.com>,
        Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
        Liam Girdwood <liam.r.girdwood@...ux.intel.com>,
        Jie Yang <yang.jie@...ux.intel.com>,
        Jaroslav Kysela <perex@...ex.cz>,
        Takashi Iwai <tiwai@...e.com>, cujomalainey@...omium.org,
        Łukasz Majczak <lmajczak@...gle.com>
Subject: Re: [PATCH] ASoC: Intel: kbl_rt5663_max98927: Fix kabylake_ssp_fixup
 function

On Mon, Oct 26, 2020 at 10:27:47PM +0000, Tomasz Figa wrote:
> On Wed, Oct 14, 2020 at 08:02:26PM +0100, Mark Brown wrote:

> > Please think hard before including complete backtraces in upstream
> > reports, they are very large and contain almost no useful information
> > relative to their size so often obscure the relevant content in your
> > message. If part of the backtrace is usefully illustrative (it often is
> > for search engines if nothing else) then it's usually better to pull out
> > the relevant sections.

> Okay, I'll trim things down next time. Somehow I was convinced it's a
> common practice.

It is unfortunately far more common than it should be but that doesn't
mean that it's a good idea!

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)