All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lafan Mining <lkfan@protonmail.com>
To: "kernelnewbies@kernelnewbies.org" <kernelnewbies@kernelnewbies.org>
Subject: Kernel upstream compile error at drivers/staging/media
Date: Wed, 08 Sep 2021 09:39:15 +0000	[thread overview]
Message-ID: <RFdLiI6S9ZQUv3CsA9aRVprm-vG-rcBtaVYTE-GTI2Pv7LhPbHZPsQakqZLaAFZ6KmhYPb581w3Vy_4l-E7nO1gEzBhrM4PI-cMuilPr57M=@protonmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 585 bytes --]

Hello!

I'm learning the Linux Kernel and currently faced troubles with building the upstream. I git clone'd source code of master and tried to make deb-pkg. I faced compile error:

drivers/staging/media/atomisp/pci/hive_isp_css_common/host/input_system.c: In function ‘input_system_configure_channel_sensor’:
drivers/staging/media/atomisp/pci/hive_isp_css_common/host/input_system.c:1649:1: error: control reaches end of non-void function [-Werror=return-type]
1649 | }

What this error could be about and how to fix it? Maybe some wrong compilation flag is the cause?

Thank you!

[-- Attachment #1.2: Type: text/html, Size: 852 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

             reply	other threads:[~2021-09-08  9:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-08  9:39 Lafan Mining [this message]
2021-09-08  9:50 ` Kernel upstream compile error at drivers/staging/media Greg KH
2021-09-08 10:02   ` Lafan Mining
2021-09-08 10:06     ` Greg KH
2021-09-08 10:36       ` Lafan Mining
2021-09-08 15:59   ` Lafan Mining
2021-09-08 16:19     ` Lukas Bulwahn
2021-09-10 10:31       ` Lafan Mining
2021-09-10 10:52         ` Lukas Bulwahn

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='RFdLiI6S9ZQUv3CsA9aRVprm-vG-rcBtaVYTE-GTI2Pv7LhPbHZPsQakqZLaAFZ6KmhYPb581w3Vy_4l-E7nO1gEzBhrM4PI-cMuilPr57M=@protonmail.com' \
    --to=lkfan@protonmail.com \
    --cc=kernelnewbies@kernelnewbies.org \
    /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.