From: Jassi Brar <jaswinder.singh@linaro.org>
To: Thierry Reding <treding@nvidia.com>
Cc: linaro-kernel@lists.linaro.org,
kernel-build-reports@lists.linaro.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mark Brown <broonie@kernel.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: next-20190215 build: 2 failures 19 warnings (next-20190215)
Date: Mon, 18 Feb 2019 11:10:14 -0600 [thread overview]
Message-ID: <CAJe_ZheryjH8EPy+gmBnnXzYWZZO+gXXCYnR7ysQexa9i4rBcQ@mail.gmail.com> (raw)
In-Reply-To: <20190218150853.GA21119@ulmo>
On Mon, 18 Feb 2019 at 09:08, Thierry Reding <treding@nvidia.com> wrote:
>
> On Mon, Feb 18, 2019 at 01:09:21PM +0100, Greg Kroah-Hartman wrote:
> > On Mon, Feb 18, 2019 at 11:32:17AM +0000, Mark Brown wrote:
> > > On Fri, Feb 15, 2019 at 08:51:48PM +0000, Build bot for Mark Brown wrote:
> > >
> > > The build failure with mbox_fush() in the tegra-tcu driver that was
> > > initially reported two weeks ago is still present in -next (this report
> > > is from Friday but it's also present today):
> > >
> > > > arm64-allmodconfig
> > > > ERROR: "mbox_flush" [drivers/tty/serial/tegra-tcu.ko] undefined!
> > > >
> > > > arm-allmodconfig
> > > > ERROR: "mbox_flush" [drivers/tty/serial/tegra-tcu.ko] undefined!
> > >
> > > Is there any progress on getting a fix merged?
> >
> > I can take the fix in my tty tree if I get an ack from the mbox
> > maintainer...
>
Not sure if I was on the CC. Honestly I only look into emails that
pass my very lenient filter. I will add 'mbox' too to it.
> Maybe we can do the below until Jassi picks up the proper fix. There is
> no hardware currently where we'd want to build the TCU driver as a
> loadable module, so that would be fine for now.
>
> It's a bit of churn because I'd want to revert that later on, but it's
> not too bad and would get linux-next back on track.
>
Maybe it should be indeed bool or rather directly selected by your
ARCH because iirc you wanted to send critical debugging messages over
tcu ;)
Anyway, I have sent a pull request with this fix in.
Cheers!
prev parent reply other threads:[~2019-02-18 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1gukSa-0003kX-JD@optimist>
2019-02-18 11:32 ` next-20190215 build: 2 failures 19 warnings (next-20190215) Mark Brown
2019-02-18 12:09 ` Greg Kroah-Hartman
2019-02-18 15:08 ` Thierry Reding
2019-02-18 17:10 ` Jassi Brar [this message]
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=CAJe_ZheryjH8EPy+gmBnnXzYWZZO+gXXCYnR7ysQexa9i4rBcQ@mail.gmail.com \
--to=jaswinder.singh@linaro.org \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=treding@nvidia.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;
as well as URLs for NNTP newsgroup(s).