[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190514181233.GB109557@google.com>
Date: Tue, 14 May 2019 11:12:33 -0700
From: Brendan Higgins <brendanhiggins@...gle.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: frowand.list@...il.com, gregkh@...uxfoundation.org,
keescook@...gle.com, kieran.bingham@...asonboard.com,
mcgrof@...nel.org, robh@...nel.org, sboyd@...nel.org,
shuah@...nel.org, tytso@....edu, yamada.masahiro@...ionext.com,
Josh Poimboeuf <jpoimboe@...hat.com>,
devicetree@...r.kernel.org, dri-devel@...ts.freedesktop.org,
kunit-dev@...glegroups.com, linux-doc@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-kbuild@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org,
linux-nvdimm@...ts.01.org, linux-um@...ts.infradead.org,
Alexander.Levin@...rosoft.com, Tim.Bird@...y.com,
amir73il@...il.com, dan.carpenter@...cle.com,
dan.j.williams@...el.com, daniel@...ll.ch, jdike@...toit.com,
joel@....id.au, julia.lawall@...6.fr, khilman@...libre.com,
knut.omang@...cle.com, logang@...tatee.com, mpe@...erman.id.au,
pmladek@...e.com, rdunlap@...radead.org, richard@....at,
rientjes@...gle.com, rostedt@...dmis.org, wfg@...ux.intel.com,
kbuild test robot <lkp@...el.com>
Subject: Re: [PATCH v3 08/18] objtool: add kunit_try_catch_throw to the
noreturn list
On Tue, May 14, 2019 at 10:46:55AM +0200, Peter Zijlstra wrote:
> On Tue, May 14, 2019 at 01:12:23AM -0700, Brendan Higgins wrote:
> > On Tue, May 14, 2019 at 08:56:43AM +0200, Peter Zijlstra wrote:
> > > On Mon, May 13, 2019 at 10:42:42PM -0700, Brendan Higgins wrote:
> > > > This fixes the following warning seen on GCC 7.3:
> > > > kunit/test-test.o: warning: objtool: kunit_test_unsuccessful_try() falls through to next function kunit_test_catch()
> > > >
> > >
> > > What is that file and function; no kernel tree near me seems to have
> > > that.
> >
> > Oh, sorry about that. The function is added in the following patch,
> > "[PATCH v3 09/18] kunit: test: add support for test abort"[1].
> >
> > My apologies if this patch is supposed to come after it in sequence, but
> > I assumed it should come before otherwise objtool would complain about
> > the symbol when it is introduced.
>
> Or send me all patches such that I have context, or have a sane
> Changelog that gives me context. Just don't give me one patch with a
> crappy changelog.
I will provide more context in the next revision.
Sorry about that!
Powered by blists - more mailing lists