Kernel upstream compile error at drivers/staging/media

Lukas Bulwahn lukas.bulwahn at
Wed Sep 8 12:19:58 EDT 2021

On Wed, Sep 8, 2021 at 6:00 PM Lafan Mining <lkfan at> wrote:
> On Wednesday, September 8th, 2021 at 12:50, Greg KH <greg at> wrote:
> > Please update your kernel version, this should already be fixed.
> It's not. There have been sent several patches already to fix this issue. Here are 2 of them:
> 1.
> 2.
> And no one of them has been applied yet. Here is the log of the file input_system.c:

Good own investigation so far.

The patch you point out is already applied to a maintainer's (Mauro's)
integration tree, and hence in linux-next:

commit 05344a1d2ea7bad3492c34299c37407bfcfed355
Author: Arnd Bergmann <arnd at>
Date:   Mon Aug 2 16:38:14 2021 +0200

    media: atomisp: restore missing 'return' statement

    The input_system_configure_channel_sensor() function lost its final
    return code in a previous patch:

In function 'input_system_configure_channel_sensor':
error: control reaches end of non-void function [-Werror=return-type]

    Restore what was there originally.

    Fixes: 728a5c64ae5f ("media: atomisp: remove dublicate code")
    Signed-off-by: Arnd Bergmann <arnd at>
    Acked-by: Sakari Ailus <sakari.ailus at>
    Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei at>

So, it is just a matter of hours until Linus takes the pull request
from Mauro, v5.15-rc1 is out and the issue is resolved. If you ping
Greg with this patch being good for stable, he will pick it and
probably apply that for the v5.14 stable tree as well.

So be a bit patient, or change your config... Do you really need this
driver? Is it really important to you and your business? Then,
consider that it is currently under drivers/staging/ and might just
disappear from one day to another because nobody is aware of critical
users (that is why it is in staging in the first place).

I hope this helps,


More information about the Kernelnewbies mailing list