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!