From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: "Luis R. Rodriguez" <mcgrof@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Nicholas Piggin <npiggin@gmail.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Fengguang Wu <fengguang.wu@intel.com>,
Adrian Hunter <adrian.hunter@intel.com>,
David Ahern <dsahern@gmail.com>, Jiri Olsa <jolsa@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Wang Nan <wangnan0@huawei.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Borislav Petkov <bp@alien8.de>
Subject: Re: linker-tables v5 testing
Date: Wed, 30 Nov 2016 02:33:49 +0100 [thread overview]
Message-ID: <20161130013349.GN1402@wotan.suse.de> (raw)
In-Reply-To: <f9e3abc8-fc5f-df73-4ddf-6f7a7b4a9112@roeck-us.net>
On Thu, Nov 24, 2016 at 08:18:40AM -0800, Guenter Roeck wrote:
> Hi Luis,
>
> On 11/23/2016 08:11 PM, Luis R. Rodriguez wrote:
> > Guenter,
> >
> > I think I'm ready to start pushing a new patch set out for review.
> > Before I do that -- can I trouble you for letting your test
> > infrastructure hammer it? I'll only push out the patches for review
> > based on this new set of changes once all tests come back OK for all
> > architectures.
> >
> > https://git.kernel.org/cgit/linux/kernel/git/mcgrof/linux-next.git/log/?h=20161117-linker-tables-v5
> >
> > Fenguang & Guenter,
> >
> > Any chance I can trouble you to enable the new driver:
> > CONFIG_TEST_LINKTABLES=y on each kernel configuration as it will run a
> > test driver which will WARN_ON() if it finds any errors.
> >
>
> I see a number of compile failures as well as some crashes in your test driver.
> Please have a look. http://kerneltests.org/builders, column 'testing'.
>
Thanks! I believe I have addressed most issues.. Any chance I can have you re-try with
this new branch:
https://git.kernel.org/cgit/linux/kernel/git/mcgrof/linux-next.git/log/?h=20161117-linker-tables-v5-try2
Luis
next prev parent reply other threads:[~2016-11-30 1:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 4:11 Luis R. Rodriguez
2016-11-24 4:57 ` Guenter Roeck
2016-11-24 16:18 ` Guenter Roeck
2016-11-30 1:33 ` Luis R. Rodriguez [this message]
2016-11-30 3:09 ` Nicholas Piggin
2016-11-30 17:38 ` Luis R. Rodriguez
2016-12-01 2:51 ` Nicholas Piggin
2016-12-01 3:15 ` Luis R. Rodriguez
2016-12-01 5:04 ` Nicholas Piggin
2016-12-01 5:20 ` Nicholas Piggin
2016-12-01 16:34 ` Luis R. Rodriguez
[not found] ` <CANashXMF3jWNgxaSQLRg2b88fSo1xEw-CDFQ6D94eoNn=mYuHQ@mail.gmail.com>
[not found] ` <CANashXOkLvy6BHupz8r-yNvihbohoXdrSQ38uq3jg2q3bGjX_w@mail.gmail.com>
[not found] ` <CANashXOb2jGtXr3BmxVKERPDp-DAHtZXYneZDEf07YpMmoqb-w@mail.gmail.com>
2016-12-02 15:49 ` Luis R. Rodriguez
2016-12-09 2:11 ` Nicholas Piggin
2016-12-02 20:20 ` Luis R. Rodriguez
2016-11-30 4:17 ` Guenter Roeck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161130013349.GN1402@wotan.suse.de \
--to=mcgrof@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=bp@alien8.de \
--cc=dsahern@gmail.com \
--cc=fengguang.wu@intel.com \
--cc=hpa@zytor.com \
--cc=jolsa@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mhiramat@kernel.org \
--cc=namhyung@kernel.org \
--cc=npiggin@gmail.com \
--cc=wangnan0@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome