From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mark Brown <broonie@kernel.org>
Cc: linaro-kernel@lists.linaro.org,
kernel-build-reports@lists.linaro.org,
Jassi Brar <jaswinder.singh@linaro.org>,
linux-next@vger.kernel.org, linux-tegra@vger.kernel.org,
Thierry Reding <treding@nvidia.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: next-20190215 build: 2 failures 19 warnings (next-20190215)
Date: Mon, 18 Feb 2019 13:09:21 +0100 [thread overview]
Message-ID: <20190218120921.GA11524@kroah.com> (raw)
In-Reply-To: <20190218113217.GA10794@sirena.org.uk>
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...
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mark Brown <broonie@kernel.org>
Cc: linaro-kernel@lists.linaro.org,
kernel-build-reports@lists.linaro.org,
Jassi Brar <jaswinder.singh@linaro.org>,
linux-next@vger.kernel.org, linux-tegra@vger.kernel.org,
Thierry Reding <treding@nvidia.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: next-20190215 build: 2 failures 19 warnings (next-20190215)
Date: Mon, 18 Feb 2019 13:09:21 +0100 [thread overview]
Message-ID: <20190218120921.GA11524@kroah.com> (raw)
In-Reply-To: <20190218113217.GA10794@sirena.org.uk>
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...
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-02-18 12:09 UTC|newest]
Thread overview: 6+ 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 [this message]
2019-02-18 12:09 ` Greg Kroah-Hartman
2019-02-18 15:08 ` Thierry Reding
2019-02-18 17:10 ` Jassi Brar
2019-02-18 17:10 ` Jassi Brar
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=20190218120921.GA11524@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=broonie@kernel.org \
--cc=jaswinder.singh@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.