[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKwvOd=D=LWeSGYekOc9qs_aVOD_jpM2DVZO7=n_2L75Ad3Nxg@mail.gmail.com>
Date: Mon, 31 Aug 2020 11:39:14 -0700
From: Nick Desaulniers <ndesaulniers@...gle.com>
To: Tom Rix <trix@...hat.com>
Cc: Vinod Koul <vkoul@...nel.org>, yung-chuan.liao@...ux.intel.com,
Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
Sanyog Kale <sanyog.r.kale@...el.com>,
Nathan Chancellor <natechancellor@...il.com>,
shreyas.nc@...el.com, alsa-devel@...a-project.org,
LKML <linux-kernel@...r.kernel.org>,
clang-built-linux <clang-built-linux@...glegroups.com>
Subject: Re: [PATCH] soundwire: fix error handling
On Mon, Aug 31, 2020 at 11:20 AM Tom Rix <trix@...hat.com> wrote:
>
>
> On 8/31/20 10:48 AM, Nick Desaulniers wrote:
> > On Mon, Aug 31, 2020 at 10:47 AM Nick Desaulniers
> > <ndesaulniers@...gle.com> wrote:
> >> On Sat, Aug 29, 2020 at 8:35 AM <trix@...hat.com> wrote:
> >>> From: Tom Rix <trix@...hat.com>
> >>>
> >>> clang static analysis flags this problem
> > Also, Tom, please use ./scripts/get_maintainer.pl on your patches to
> > CC our mailing list; clang-built-linux@...glegroups.com.
>
> gcc is still doing the building, so it this appropriate ?
>
> Asking because i have been sed-ing clang-build-linux out.
ah, right, you can use `--use-cc=clang` for analyses of builds with
clang. It doesn't hurt to include our mailing list, since we'd like
to know if issues get reported with the analyzer itself.
--
Thanks,
~Nick Desaulniers
Powered by blists - more mailing lists